{"push_id":672634236,"size":496,"distinct_size":496,"ref":"refs/heads/android-msm-2.6.36-jbdev","head":"61b4a9e173377cf10243900723d43345ec21c2de","before":"f3012ae940961c954faffea70d98cf0dc5ec1515","commits":[{"sha":"61a85d5fae3a1b57b9cebcba34958dc27dd8d202","author":{"email":"428a1e03bf18d7720952a3563b48222e4a94a135@infradead.org","name":"Jan Blunck"},"message":"BKL: Remove BKL from ext4 filesystem\n\nThe BKL is still used in ext4_put_super(), ext4_fill_super() and\next4_remount(). All three calles are protected against concurrent calls by\nthe s_umount rw semaphore of struct super_block.\n\nTherefore the BKL is protecting nothing in this case.\n\nSigned-off-by: Jan Blunck <jblunck@infradead.org>\nAcked-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/61a85d5fae3a1b57b9cebcba34958dc27dd8d202"},{"sha":"ec310dadf54ba551f16520c901a7861bc219f978","author":{"email":"428a1e03bf18d7720952a3563b48222e4a94a135@infradead.org","name":"Jan Blunck"},"message":"BKL: Remove BKL from HFS\n\nThe BKL is only used in put_super and fill_super that are both protected by\nthe superblocks s_umount rw_semaphore. Therefore it is safe to remove the\nBKL entirely.\n\nSigned-off-by: Jan Blunck <jblunck@infradead.org>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/ec310dadf54ba551f16520c901a7861bc219f978"},{"sha":"5ca11016f93273c447db348eadfbf16ba3f9e91b","author":{"email":"428a1e03bf18d7720952a3563b48222e4a94a135@infradead.org","name":"Jan Blunck"},"message":"BKL: Remove BKL from JFS\n\nThe BKL is only used in put_super, fill_super and remount_fs that are all\nthree protected by the superblocks s_umount rw_semaphore. Therefore it is\nsafe to remove the BKL entirely.\n\nSigned-off-by: Jan Blunck <jblunck@infradead.org>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/5ca11016f93273c447db348eadfbf16ba3f9e91b"},{"sha":"47328fc0d56f299a127aa4f8ac43463e01e5db6f","author":{"email":"428a1e03bf18d7720952a3563b48222e4a94a135@infradead.org","name":"Jan Blunck"},"message":"BKL: Remove BKL from NILFS2\n\nThe BKL is only used in put_super, fill_super and remount_fs that are all\nthree protected by the superblocks s_umount rw_semaphore. Therefore it is\nsafe to remove the BKL entirely.\n\nSigned-off-by: Jan Blunck <jblunck@infradead.org>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/47328fc0d56f299a127aa4f8ac43463e01e5db6f"},{"sha":"0ad19cef9620732e3467245d371b7695aa187e73","author":{"email":"428a1e03bf18d7720952a3563b48222e4a94a135@infradead.org","name":"Jan Blunck"},"message":"BKL: Remove BKL from NTFS\n\nThe BKL is only used in put_super, fill_super and remount_fs that are all\nthree protected by the superblocks s_umount rw_semaphore. Therefore it is\nsafe to remove the BKL entirely.\n\nSigned-off-by: Jan Blunck <jblunck@infradead.org>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/0ad19cef9620732e3467245d371b7695aa187e73"},{"sha":"9d3e60c877eaf1903b252d10daad6027d1ef0cd2","author":{"email":"428a1e03bf18d7720952a3563b48222e4a94a135@infradead.org","name":"Jan Blunck"},"message":"BKL: Remove BKL from cgroup\n\nThe BKL is only used in remount_fs and get_sb that are both protected by\nthe superblocks s_umount rw_semaphore. Therefore it is safe to remove the\nBKL entirely.\n\nSigned-off-by: Jan Blunck <jblunck@infradead.org>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/9d3e60c877eaf1903b252d10daad6027d1ef0cd2"},{"sha":"77bfe1e5a3ab419d82c2e8baddd2e1080e6a03c8","author":{"email":"428a1e03bf18d7720952a3563b48222e4a94a135@infradead.org","name":"Jan Blunck"},"message":"BKL: Remove BKL from do_new_mount()\n\nAfter pushing down the BKL to the get_sb/fill_super operations of the\nfilesystems that still make usage of the BKL it is safe to remove it from\ndo_new_mount().\n\nI've read through all the code formerly covered by the BKL inside\ndo_kern_mount() and have satisfied myself that it doesn't need the BKL\nany more.\n\nSigned-off-by: Jan Blunck <jblunck@infradead.org>\nCc: Matthew Wilcox <matthew@wil.cx>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/77bfe1e5a3ab419d82c2e8baddd2e1080e6a03c8"},{"sha":"160803207b1ff91b8f5c48daaea095d81fa1053c","author":{"email":"428a1e03bf18d7720952a3563b48222e4a94a135@infradead.org","name":"Jan Blunck"},"message":"BKL: Remove BKL from ext2 filesystem\n\nThe BKL is still used in ext2_put_super(), ext2_fill_super(), ext2_sync_fs()\next2_remount() and ext2_write_inode(). From these calls ext2_put_super(),\next2_fill_super() and ext2_remount() are protected against each other by\nthe struct super_block s_umount rw semaphore. The call in ext2_write_inode()\ncould only protect the modification of the ext2_sb_info through\next2_update_dynamic_rev() against concurrent ext2_sync_fs() or ext2_remount().\next2_fill_super() and ext2_put_super() can be left out because you need a\nvalid filesystem reference in all three cases, which you do not have when\nyou are one of these functions.\n\nIf the BKL is only protecting the modification of the ext2_sb_info it can\nsafely be removed since this is protected by the struct ext2_sb_info s_lock.\n\nSigned-off-by: Jan Blunck <jblunck@infradead.org>\nCc: Jan Kara <jack@suse.cz>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/160803207b1ff91b8f5c48daaea095d81fa1053c"},{"sha":"4c35f201efef491fe3a8657202b817be2b56e18b","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from fat\n\nThe lock_kernel in fat_put_super is not needed because\nit only protects the super block itself and we know that\nno other thread can reach it because we are about to\nkfree the object.\n\nIn the two fill_super functions, this converts the locking\nto use lock_super like elsewhere in the fat code. This\nis probably not needed either, but is consistent and puts\nus on the safe side.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nCc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>\nCc: Jan Blunck <jblunck@infradead.org>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/4c35f201efef491fe3a8657202b817be2b56e18b"},{"sha":"915313b239aab7877b9792dd27919f2dcbd83b72","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from isofs\n\nAs in other file systems, we can replace the big kernel lock\nwith a private mutex in isofs. This means we can now access\nmultiple file systems concurrently, but it also means that\nwe serialize readdir and lookup across sleeping operations\nwhich previously released the big kernel lock. This should\nnot matter though, as these operations are in practice\nserialized through the hardware access.\n\nThe isofs_get_blocks functions now does not take any lock\nany more, it used to recursively get the BKL. After looking\nat the code for hours, I convinced myself that it was never\nneeded here anyway, because it only reads constant fields\nof the inode and writes to a buffer head array that is\nat this time only visible to the caller.\n\nThe get_sb and fill_super operations do not need the locking\nat all because they operate on a file system that is either\nabout to be created or to be destroyed but in either case\nis not visible to other threads.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/915313b239aab7877b9792dd27919f2dcbd83b72"},{"sha":"3e1c9df3dad21093ca3715812705a6ce71ae3347","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from autofs4\n\nautofs4 uses the BKL only to guard its ioctl operations.\nThis can be trivially converted to use a mutex, as we have\ndone with most device drivers before.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nCc: \"H. Peter Anvin\" <hpa@zytor.com>\nCc: Ian Kent <raven@themaw.net>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/3e1c9df3dad21093ca3715812705a6ce71ae3347"},{"sha":"707a8b0a36cf6c6b900a06dd007256b55f32de69","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from USB gadgetfs\n\nThe BKL is only used in fill_super, which is  protected by the superblocks\ns_umount rw_semaphore. Therefore it is safe to remove the BKL entirely.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nCc: David Brownell <dbrownell@users.sourceforge.net>\nCc: linux-usb@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/707a8b0a36cf6c6b900a06dd007256b55f32de69"},{"sha":"a157a8798a4b9a64fdf3ce547339c5069e70d891","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from afs\n\nThe BKL is only used in put_super and fill_super, which are both protected\nby the superblocks s_umount rw_semaphore. Therefore it is safe to remove\nthe BKL entirely.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nCc: linux-afs@lists.infradead.org\nCc: David Howells <dhowells@redhat.com>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/a157a8798a4b9a64fdf3ce547339c5069e70d891"},{"sha":"1cca2742878ebb285c4d3344ba158b946b97775d","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from ecryptfs\n\nThe BKL is only used in fill_super, which is protected by the superblocks\ns_umount rw_semaphorei, and in fasync, which does not do anything that\ncould require the BKL. Therefore it is safe to remove the BKL entirely.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nCc: Dustin Kirkland <kirkland@canonical.com>\nCc: Tyler Hicks <tyhicks@linux.vnet.ibm.com>\nCc: ecryptfs-devel@lists.launchpad.net","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/1cca2742878ebb285c4d3344ba158b946b97775d"},{"sha":"19e20dae75da57fc6e482effaa0ffb9592bdf574","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from jffs2\n\nThe BKL is only used in put_super, fill_super and remount_fs that are all\nthree protected by the superblocks s_umount rw_semaphore. Therefore it is\nsafe to remove the BKL entirely.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nCc: David Woodhouse <dwmw2@infradead.org>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/19e20dae75da57fc6e482effaa0ffb9592bdf574"},{"sha":"e75e77f5458d9476f818790d2bb778e3d9c78ceb","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from squashfs\n\nThe BKL is only used in put_super and fill_super, which are both protected\nby the superblocks s_umount rw_semaphore. Therefore it is safe to remove\nthe BKL entirely.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nCc: Phillip Lougher <phillip@lougher.demon.co.uk>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/e75e77f5458d9476f818790d2bb778e3d9c78ceb"},{"sha":"b1bd5e134308bf49b5e156aeadc224d4fc63bdf4","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"BKL: Remove BKL from OCFS2\n\nThe BKL in ocfs2/dlmfs is used in put_super, fill_super and remount_fs\nthat are all three protected by the superblocks s_umount rw_semaphore.\n\nThe use in ocfs2_control_open is evidently unrelated and the function\nis protected by ocfs2_control_lock.\n\nTherefore it is safe to remove the BKL entirely.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nCc: Mark Fasheh <mfasheh@suse.com>\nCc: Joel Becker <joel.becker@oracle.com>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/b1bd5e134308bf49b5e156aeadc224d4fc63bdf4"},{"sha":"42551625563ce67fa4ca3eb1818fab591dd1d291","author":{"email":"c327e92ea10f7773037429ba850de356a617881c@vandrovec.name","name":"Petr Vandrovec"},"message":"BKL: Remove BKL from ncpfs\n\nDozen of changes in ncpfs to provide some locking other than BKL.\n\nIn readdir cache unlock and mark complete first page as last operation,\nso it can be used for synchronization, as code intended.\n\nWhen updating dentry name on case insensitive filesystems do at least\nsome basic locking...\n\nHold i_mutex when updating inode fields.\n\nPush some ncp_conn_is_valid down to ncp_request.  Connection can become\ninvalid at any moment, and fewer error code paths to test the better.\n\nUse i_size_{read,write} to modify file size.\n\nSet inode's backing_dev_info as ncpfs has its own special bdi.\n\nIn ioctl unbreak ioctls invoked on filesystem mounted 'ro' - tests are\nfor inode writeable or owner match, but were turned to filesystem\nwriteable and inode writeable or owner match.  Also collect all permission\nchecks in single place.\n\nAdd some locking, and remove comments saying that it would be cool to\nadd some locks to the code.\n\nConstify some pointers.\n\nSigned-off-by: Petr Vandrovec <petr@vandrovec.name>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/42551625563ce67fa4ca3eb1818fab591dd1d291"},{"sha":"dd2ad789faf3b8604942d952fa57f4644185a61b","author":{"email":"ad427779d5c7c816b5649657d7449a50ef7f9847@slind.org","name":"Alexander Shishkin"},"message":"ARM: 6291/1: coresight: move struct tracectx inside etm driver\n\nThis is done so as to be able to make use of the coresight components'\nregisters in assembler code (like omap sleep code). Also, there shouldn't\nbe any users of this structure outside the etm driver.\n\nCc: linux-arm-kernel@lists.infradead.org\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Alexander Shishkin <virtuoso@slind.org>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/dd2ad789faf3b8604942d952fa57f4644185a61b"},{"sha":"d049620067597ff0eea2039caa1d08a9f59c5f36","author":{"email":"ad427779d5c7c816b5649657d7449a50ef7f9847@slind.org","name":"Alexander Shishkin"},"message":"ARM: 6293/1: coresight: cosmetic fixes\n\nUse BIT() macro whenever it is sensible to do so.\n\nCc: linux-arm-kernel@lists.infradead.org\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Alexander Shishkin <virtuoso@slind.org>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/steppnasty/htc-kernel-msm7x30/commits/d049620067597ff0eea2039caa1d08a9f59c5f36"}]}