GitHub PushEvent at 2014-11-05 22:54:53
Repository: Dorimanx-LG-G2-D802-Kernel
Actor: dorimanx
Payload: {"shas":[["5b624a0ddf5dbc4565634252ac8240d3b89a9688","69d4c67d027719823df1f8f9226c47bc05dc8998@linux.vnet.ibm.com","debugfs: Add support to print u32 array in debugfs\n\nMove the code from Xen to debugfs to make the code common\nfor other users as well.\n\nAccked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>\nSigned-off-by: Suzuki Poulose <suzuki@in.ibm.com>\n[v1: Fixed rebase issues]\n[v2: Fixed PPC compile issues]\nSigned-off-by: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>","Srivatsa Vaddagiri",true],["89ba1c070909c5be285fc683015079b0e36a30b1","d8cd2994e15bc61ddb2b113030bda55eebc3a0fe@google.com","debugfs: fix race in u32_array_read and allocate array at open\n\nu32_array_open() is racy when multiple threads read from a file with a\nseek position of zero, i.e. when two or more simultaneous reads are\noccurring after the non-seekable files are created.  It is possible that\nfile->private_data is double-freed because the threads races between\n\n\tkfree(file->private-data);\n\nand\n\n\tfile->private_data = NULL;\n\nThe fix is to only do format_array_alloc() when the file is opened and\nfree it when it is closed.\n\nNote that because the file has always been non-seekable, you can't open\nit and read it multiple times anyway, so the data has always been\ngenerated just once.  The difference is that now it is generated at open\ntime rather than at the time of the first read, and that avoids the\nrace.\n\nReported-by: Dave Jones <davej@redhat.com>\nAcked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nTested-by: Raghavendra <raghavendra.kt@linux.vnet.ibm.com>\nSigned-off-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","David Rientjes",true],["795942c746e029c91af3c150f7cf0d159a754ce0","69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","debugfs: fix u32_array race in format_array_alloc\n\nThe format_array_alloc() function is fundamentally racy, in that it\nprints the array twice: once to figure out how much space to allocate\nfor the buffer, and the second time to actually print out the data.\n\nIf any of the array contents changes in between, the allocation size may\nbe wrong, and the end result may be truncated in odd ways.\n\nJust don't do it.  Allocate a maximum-sized array up-front, and just\nformat the array contents once.  The only user of the u32_array\ninterfaces is the Xen spinlock statistics code, and it has 31 entries in\nthe arrays, so the maximum size really isn't that big, and the end\nresult is much simpler code without the bug.\n\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","Linus Torvalds",true],["ee46f81b2c66b85afbb03ff7d4741b178764ac33","06447fbe43693466d3293d0b5eaeeb2efd3d7d3a@broadcom.com","debugfs: change parameter check in debugfs_remove() functions\n\nThe dentry parameter in debugfs_remove() and debugfs_remove_recursive()\nis checked being a NULL pointer. To make cleanup by callers easier this\ncheck is extended using the IS_ERR_OR_NULL macro instead because the\ndebugfs_create_... functions can return a ERR_PTR() value.\n\nSigned-off-by: Arend van Spriel <arend@broadcom.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Arend van Spriel",true],["55dd1d950f2a7e7ba8661de8891aaae7a7ef95bd","de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","debugfs: make sure that debugfs_create_file() gets used only for regulars\n\nIt, debugfs_create_dir() and debugfs_create_link() use the common helper\nnow.\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","Al Viro",true],["8f232165fbecae4046c8172c13bbb8807f0932f9","de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","debugfs: fold debugfs_create_by_name() into the only caller\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","Al Viro",true],["d1bad50405faee2d5345abf043e9f32dacb01678","de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","debugfs: get rid of useless arguments to debugfs_{mkdir,symlink}\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","Al Viro",true],["1279cc1972a7139cacedd590a6a3db98be0f2a6f","e829bd48de90b6e1a1950750fa8ca2bb62f273d4@sous-sol.org","debugfs: make __create_file static\n\nIt's only used locally, no need to pollute global namespace.\n\nSigned-off-by: Chris Wright <chrisw@sous-sol.org>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Chris Wright",true],["5f1c82b005a8fde85aa307228866e3bc5aa04f53","de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk","->encode_fh() API change\n\npass inode + parent's inode or NULL instead of dentry + bool saying\nwhether we want the parent or not.\n\nNOTE: that needs ceph fix folded in.\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>","Al Viro",true],["164bdcef5325abb078c14cad7beaeba31282a356","2f96f8cd3e2780a209d0ab27d1b44624d0019d3f@linux.intel.com","fat: introduce special inode for managing the FSINFO block\n\nThis is patchset makes fatfs stop using the VFS '->write_super()' method\nfor writing out the FSINFO block.\n\nThe final goal is to get rid of the 'sync_supers()' kernel thread.  This\nkernel thread wakes up every 5 seconds (by default) and calls\n'->write_super()' for all mounted file-systems.  And the bad thing is that\nthis is done even if all the superblocks are clean.  Moreover, some\nfile-systems do not even need this end they do not register the\n'->write_super()' method at all (e.g., btrfs).\n\nSo 'sync_supers()' most often just generates useless wake-ups and wastes\npower.  I am trying to make all file-systems independent of\n'->write_super()' and plan to remove 'sync_supers()' and '->write_super'\ncompletely once there are no more users.\n\nThe '->write_supers()' method is mostly used by baroque file-systems like\nhfs, udf, etc.  Modern file-systems like btrfs and xfs do not use it.\nThis justifies removing this stuff from VFS completely and make every FS\nself-manage own superblock.\n\nTested with xfstests.\n\nThis patch:\n\nPreparation for further changes.  It introduces a special inode\n('fsinfo_inode') in FAT file-system which we'll later use for managing the\nFSINFO block.  Note, this there is already one special inode ('fat_inode')\nwhich is used for managing the FAT tables.\n\nIntroduce new 'MSDOS_FSINFO_INO' constant for this special inode.  It is\nsafe to do because FAT file-system does not store inode numbers on the\nmedia but generates them run-time.\n\nI've also cleaned up the comment to existing 'MSDOS_ROOT_INO' constant,\nwhile on it.\n\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nCc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>\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>","Artem Bityutskiy",true],["e5780308b0d03888cc0d37e95d23206fa039a572","2f96f8cd3e2780a209d0ab27d1b44624d0019d3f@linux.intel.com","fat: introduce mark_fsinfo_dirty helper\n\nA preparation patch which introduces a 'mark_fsinfo_dirty()' helper\nfunction which just sets the 's_dirt' flag to 1 so far.  I'll add more\ncode to this helper later, so I do not mark it as 'inline'.\n\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nCc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>\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>","Artem Bityutskiy",true],["1a301200b4164914f5d1989c5fba7da56c4520b8","2f96f8cd3e2780a209d0ab27d1b44624d0019d3f@linux.intel.com","fat: mark superblock as dirty less often\n\nPreparation for further changes.  It touches few functions in fatent.c and\nprevents them from marking the superblock as dirty unnecessarily often.\nNamely, instead of marking it as dirty in the internal tight loops - do it\nonly once at the end of the functions.  And instead of marking it as dirty\nwhile holding the FAT table lock, do it outside the lock.\n\nThe reason for this patch is that marking the superblock as dirty will\nsoon become a little bit heavier operation, so it is cleaner to do this\nonly when it is necessary.\n\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nCc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>\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>","Artem Bityutskiy",true],["3ca40fac62cac1528de838a0cc58bdf6bac7b535","2f96f8cd3e2780a209d0ab27d1b44624d0019d3f@linux.intel.com","fat: switch to fsinfo_inode\n\nCurrently FAT file-system maps the VFS \"superblock\" abstraction to the\nFSINFO block.  The FSINFO block contains non-essential data about the\namount of free clusters and the next free cluster.  FAT file-system can\nalways find out this information by scanning the FAT table, but having it\nin the FSINFO block may speed things up sometimes.  So FAT file-system\nrelies on the VFS superblock write-out services to make sure the FSINFO\nblock is written out to the media from time to time.\n\nThe whole \"superblock write-out\" VFS infrastructure is served by the\n'sync_supers()' kernel thread, which wakes up every 5 (by default) seconds\nand writes out all dirty superblock using the '->write_super()' call-back.\n But the problem with this thread is that it wastes power by waking up the\nsystem every 5 seconds no matter what.  So we want to kill it completely\nand thus, we need to make file-systems to stop using the '->write_super'\nVFS service, and then remove it together with the kernel thread.\n\nThis patch switches the FAT FSINFO block management from\n'->write_super()'/'->s_dirt' to 'fsinfo_inode'/'->write_inode'.  Now,\ninstead of setting the 's_dirt' flag, we just mark the special\n'fsinfo_inode' inode as dirty and let VFS invoke the '->write_inode'\ncall-back when needed, where we write-out the FSINFO block.\n\nThis patch also makes sure we do not mark the 'fsinfo_inode' inode as\ndirty if we are not FAT32 (FAT16 and FAT12 do not have the FSINFO block)\nor if we are in R/O mode.\n\nAs a bonus, we can also remove the '->sync_fs()' and '->write_super()' FAT\ncall-back function because they become unneeded.\n\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nCc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>\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>","Artem Bityutskiy",true],["430e5764afcb40cb8d5a3f75d5db456db6ccca42","4eaf47c25ead9675aad93689a157e819ffdaf8b3@gmail.com","fat: add fat_msg_ratelimit()\n\nAdd a fat_msg_ratelimit() to limit the message generation rate.\n\nSigned-off-by: Namjae Jeon <linkinjeon@gmail.com>\nSigned-off-by: Amit Sahrawat <amit.sahrawat83@gmail.com>\nAcked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","Namjae Jeon",true],["f8ab509175b2b54fa789ea6d50d3912712c92e4d","4eaf47c25ead9675aad93689a157e819ffdaf8b3@gmail.com","fat: use fat_msg_ratelimit() in fat__get_entry()\n\nIf an application tries to lookup (opendir/readdir/stat) 5000 files on a\nfatfs USB device and the device is unplugged, many message occur, shown\nbelow.  This makes the application slow.  So use the new\nfat_msg_ratelimit() decrease the messaging rate.\n\n  #> ./file_lookup_testcase ./files_directory/\n  usb 2-1.4: USB disconnect, device number 4\n  FAT-fs (sda1): FAT read failed (blocknr 2631)\n  FAT-fs (sda1): Directory bread(block 396816) failed\n  FAT-fs (sda1): Directory bread(block 396817) failed\n  FAT-fs (sda1): Directory bread(block 396818) failed\n  FAT-fs (sda1): Directory bread(block 396819) failed\n  FAT-fs (sda1): Directory bread(block 396820) failed\n  FAT-fs (sda1): Directory bread(block 396821) failed\n  FAT-fs (sda1): Directory bread(block 396822) failed\n  FAT-fs (sda1): Directory bread(block 396823) failed\n  FAT-fs (sda1): Directory bread(block 406824) failed\n  FAT-fs (sda1): Directory bread(block 406825) failed\n  FAT-fs (sda1): Directory bread(block 406826) failed\n  FAT-fs (sda1): Directory bread(block 406827) failed\n  FAT-fs (sda1): Directory bread(block 406828) failed\n  FAT-fs (sda1): Directory bread(block 406829) failed\n  FAT-fs (sda1): Directory bread(block 406830) failed\n  FAT-fs (sda1): Directory bread(block 406831) failed\n  FAT-fs (sda1): Directory bread(block 417696) failed\n  FAT-fs (sda1): Directory bread(block 417697) failed\n  FAT-fs (sda1): Directory bread(block 417698) failed\n  FAT-fs (sda1): Directory bread(block 417699) failed\n  FAT-fs (sda1): Directory bread(block 417700) failed\n  FAT-fs (sda1): Directory bread(block 417701) failed\n  FAT-fs (sda1): Directory bread(block 417702) failed\n  FAT-fs (sda1): Directory bread(block 417703) failed\n  FAT-fs (sda1): FAT read failed (blocknr 2631)\n  FAT-fs (sda1): Directory bread(block 396816) failed\n  FAT-fs (sda1): Directory bread(block 396817) failed\n  FAT-fs (sda1): Directory bread(block 396818) failed\n  FAT-fs (sda1): Directory bread(block 396819) failed\n  FAT-fs (sda1): Directory bread(block 396820) failed\n  FAT-fs (sda1): Directory bread(block 396821) failed\n\nSigned-off-by: Namjae Jeon <linkinjeon@gmail.com>\nSigned-off-by: Amit Sahrawat <amit.sahrawat83@gmail.com>\nAcked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","Namjae Jeon",true],["a70ff80490aba16c2f8462dcb68b8dea66dd32ad","9ce5770b3bb4b2a1d59be2d97e34379cd192299f@digidescorp.com","fat: fix non-atomic NFS i_pos read\n\nfat_encode_fh() can fetch an invalid i_pos value on systems where 64-bit\naccesses are not atomic.  Make it use the same accessor as the rest of the\nFAT code.\n\nSigned-off-by: Steven J. Magnani <steve@digidescorp.com>\nAcked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","Steven J. Magnani",true],["9f1040b279c9eeb33ad431f846cea57d29a11b9c","8d60cd65e947920c1efaaf1b4ff723c7aa255e6d@netapp.com","NFS: Remove secinfo knowledge out of the generic client\n\nAnd also remove the unneeded rpc_op.\n\nSigned-off-by: Bryan Schumaker <bjschuma@netapp.com>\nSigned-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>","Bryan Schumaker",true],["401d56c6058aacdb669bde098efa642f0db47df9","8d60cd65e947920c1efaaf1b4ff723c7aa255e6d@netapp.com","NFS: Create a submount rpc_op\n\nThis simplifies the code for v2 and v3 and gives v4 a chance to decide\non referrals without needing to modify the generic client.\n\nSigned-off-by: Bryan Schumaker <bjschuma@netapp.com>\nSigned-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>","Bryan Schumaker",true],["a0814e3b064cdfbd4dca31080f6e9c89a03b2011","8d60cd65e947920c1efaaf1b4ff723c7aa255e6d@netapp.com","NFS: Remove extra rpc_clnt argument to proc_lookup\n\nNow that I'm doing secinfo automatically in the v4 code this extra\nargument isn't needed.\n\nSigned-off-by: Bryan Schumaker <bjschuma@netapp.com>\nSigned-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>","Bryan Schumaker",true],["3bed88bdb65b6ade35493bd9747cb74e215b9f50","6a1f9db795c9fc44be97d66ab114c53193bd3d13@netapp.com","NFS: Adapt readdirplus to application usage patterns\n\nWhile the use of READDIRPLUS is significantly more efficient than\nREADDIR followed by many LOOKUP calls, it is still less efficient\nthan just READDIR if the attributes are not required.\n\nThis patch tracks when lookups are attempted on the directory,\nand uses that information to selectively disable READDIRPLUS\non that directory.\nThe first 'readdir' call is always served using READDIRPLUS.\nSubsequent calls only use READDIRPLUS if there was a successful\nlookup or revalidation on a child in the mean time.\n\nCredit for the original idea should go to Neil Brown. See:\n      http://www.spinics.net/lists/linux-nfs/msg19996.html\nHowever, the implementation in this patch differs from Neil's\nin that it focuses on tracking lookups rather than calls to\nstat().\n\nSigned-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>\nCc: Neil Brown <neilb@suse.de>","Trond Myklebust",true]],"size":46,"ref":"refs/heads/dev-fs-ok","head":"3d1d00c5e80eb2da6a380dcfc888746a8670e3a3"}