{"push_id":1091860398,"size":9,"distinct_size":9,"ref":"refs/heads/master","head":"10cbb4409959baac26e19bbd548d85b9001a7fe4","before":"1e17b0a7bd5bd3b8b12b285321fc3930a567c23f","commits":[{"sha":"cf34498145fd55ff375361d52c74e1897d3909db","author":{"email":"eecfa5af1016ca9db755569d9919e212ab6a1c94@openvz.org","name":"Dmitry Monakhov"},"message":"fs/pipe.c: skip file_update_time on frozen fs\n\nPipe has no data associated with fs so it is not good idea to block\npipe_write() if FS is frozen, but we can not update file's time on such\nfilesystem.  Let's use same idea as we use in touch_time().\n\nAddresses https://bugzilla.kernel.org/show_bug.cgi?id=65701\n\nSigned-off-by: Dmitry Monakhov <dmonakhov@openvz.org>\nReviewed-by: Jan Kara <jack@suse.cz>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/cf34498145fd55ff375361d52c74e1897d3909db"},{"sha":"2cd460bca128e6f7a02515965d7e8f68f0b51607","author":{"email":"2c473c19cb2299560280a7d1cf4bf711b19eb7c0@gmail.com","name":"Eric Biggers"},"message":"fs/pipe.c: preserve alloc_file() error code\n\nIf sys_pipe() was unable to allocate a 'struct file', it always failed\nwith ENFILE, which means \"The number of simultaneously open files in the\nsystem would exceed a system-imposed limit.\" However, alloc_file()\nactually returns an ERR_PTR value and might fail with other error codes.\nCurrently, in addition to ENFILE, it can fail with ENOMEM, potentially\nwhen there are few open files in the system.  Update sys_pipe() to\npreserve this error code.\n\nIn a prior submission of a similar patch (1) some concern was raised\nabout introducing a new error code for sys_pipe().  However, for most\nsystem calls, programs cannot assume that new error codes will never be\nintroduced.  In addition, ENOMEM was, in fact, already a possible error\ncode for sys_pipe(), in the case where the file descriptor table could\nnot be expanded due to insufficient memory.\n\n\t(1) http://comments.gmane.org/gmane.linux.kernel/1357942\n\nSigned-off-by: Eric Biggers <ebiggers3@gmail.com>\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/2cd460bca128e6f7a02515965d7e8f68f0b51607"},{"sha":"e317bbd113d197d2efd7df1188445bdd1067bc66","author":{"email":"de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","name":"Al Viro"},"message":"fuse/dev: use atomic maps\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/e317bbd113d197d2efd7df1188445bdd1067bc66"},{"sha":"a39289b9ce97d18b02710223ae98bea0a80be39d","author":{"email":"de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","name":"Al Viro"},"message":"pipe: kill ->map() and ->unmap()\n\nall pipe_buffer_operations have the same instances of those...\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/a39289b9ce97d18b02710223ae98bea0a80be39d"},{"sha":"84ae99358f7774ed6f9eafd1c95cd388bb5e9f24","author":{"email":"ebac1d06c1688626821bb0e574a037a7a5354e49@redhat.com","name":"David Howells"},"message":"VFS: assorted weird filesystems: d_inode() annotations\n\nSigned-off-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/84ae99358f7774ed6f9eafd1c95cd388bb5e9f24"},{"sha":"15b385f385dd6290c0efed5428af13eb72d342a0","author":{"email":"de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","name":"Al Viro"},"message":"kill d_validate()\n\nno users left\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/15b385f385dd6290c0efed5428af13eb72d342a0"},{"sha":"90a300af0287744e0ff3124fe6914a100c746f2a","author":{"email":"aaf6fd97230863eae371b8b6c4c40693d5d84b30@bynet.co.il","name":"Dorimanx"},"message":"cleanup include/linux/dcache.h before next commit!","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/90a300af0287744e0ff3124fe6914a100c746f2a"},{"sha":"64c8c6a03ed422593a126e03e0e995cea85e3202","author":{"email":"ebac1d06c1688626821bb0e574a037a7a5354e49@redhat.com","name":"David Howells"},"message":"VFS: Introduce inode-getting helpers for layered/unioned fs environments\n\nIntroduce some function for getting the inode (and also the dentry) in an\nenvironment where layered/unioned filesystems are in operation.\n\nThe problem is that we have places where we need *both* the union dentry and\nthe lower source or workspace inode or dentry available, but we can only have\na handle on one of them.  Therefore we need to derive the handle to the other\nfrom that.\n\nThe idea is to introduce an extra field in struct dentry that allows the union\ndentry to refer to and pin the lower dentry.\n\nSigned-off-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/64c8c6a03ed422593a126e03e0e995cea85e3202"},{"sha":"10cbb4409959baac26e19bbd548d85b9001a7fe4","author":{"email":"ebac1d06c1688626821bb0e574a037a7a5354e49@redhat.com","name":"David Howells"},"message":"VFS: Add owner-filesystem positive/negative dentry checks\n\nSupply two functions to test whether a filesystem's own dentries are positive\nor negative (d_really_is_positive() and d_really_is_negative()).\n\nThe problem is that the DCACHE_ENTRY_TYPE field of dentry->d_flags may be\noverridden by the union part of a layered filesystem and isn't thus\nnecessarily indicative of the type of dentry.\n\nNormally, this would involve a negative dentry (ie. ->d_inode == NULL) having\n->d_layer.lower pointed to a lower layer dentry, DCACHE_PINNING_LOWER set and\nthe DCACHE_ENTRY_TYPE field set to something other than DCACHE_MISS_TYPE - but\nit could also involve, say, a DCACHE_SPECIAL_TYPE being overridden to\nDCACHE_WHITEOUT_TYPE if a 0,0 chardev is detected in the top layer.\n\nHowever, inside a filesystem, when that fs is looking at its own dentries, it\nprobably wants to know if they are really negative or not - and doesn't care\nabout the fallthrough bits used by the union.\n\nTo this end, a filesystem should normally use d_really_is_positive/negative()\nwhen looking at its own dentries rather than d_is_positive/negative() and\nshould use d_inode() to get at the inode.\n\nAnyone looking at someone else's dentries (this includes pathwalk) should use\nd_is_xxx() and d_backing_inode().\n\nSigned-off-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/dorimanx/DORIMANX_LG_STOCK_LP_KERNEL/commits/10cbb4409959baac26e19bbd548d85b9001a7fe4"}]}