{"push_id":575161870,"size":227,"distinct_size":227,"ref":"refs/heads/lollipop","head":"4e5e8056d69af0442b429c21d31b8afb6284144a","before":"9514e87e8e3d4a048ca9cae7e34e00afe9535a0e","commits":[{"sha":"dc0fccd452cd524a7de8c1e9d615a55d8666a328","author":{"email":"ba92fcbca207ca7cb8cd8969e232afbece545036@gmail.com","name":"Stefanescu Cristian"},"message":"Revert \"fs: sync: add missing return if fsync is disabled from userspace.\"\n\nThis reverts commit 7fc53de7b2023bcc76a318004584a2dc04e87b10.","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/dc0fccd452cd524a7de8c1e9d615a55d8666a328"},{"sha":"8172217f4f0d9067ae180242ab9bd5642d04b7a0","author":{"email":"ba92fcbca207ca7cb8cd8969e232afbece545036@gmail.com","name":"Stefanescu Cristian"},"message":"Revert \"fs: sync: enable fsync by default.\"\n\nThis reverts commit f940ee199670b3bcc9048a8e6314f284e0a506b0.","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/8172217f4f0d9067ae180242ab9bd5642d04b7a0"},{"sha":"aaabfb7385d0c07382a7dcdad66cb46874e881ad","author":{"email":"ba92fcbca207ca7cb8cd8969e232afbece545036@gmail.com","name":"Stefanescu Cristian"},"message":"Revert \"Added fsync on/off support.\"\n\nThis reverts commit 967c7aadf200547fc7e637869211eda3af3a2806.\n\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>\n\nConflicts:\n\tfs/sync.c","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/aaabfb7385d0c07382a7dcdad66cb46874e881ad"},{"sha":"bbb6a16f66ebc3f9007e6158c3889374c902ee8b","author":{"email":"cc47c8d45a0a3c6300393e2d0c4f6e661d0cfdb0@gmail.com","name":"Yongqiang Yang"},"message":"ext4: ignore last group w/o enough space when resizing instead of BUG'ing\n\nIf the last group does not have enough space for group tables, ignore\nit instead of calling BUG_ON().\n\nReported-by: Daniel Drake <dsd@laptop.org>\nSigned-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/bbb6a16f66ebc3f9007e6158c3889374c902ee8b"},{"sha":"2d1258784205073dcba111c9ca148b3711a220ab","author":{"email":"cc47c8d45a0a3c6300393e2d0c4f6e661d0cfdb0@gmail.com","name":"Yongqiang Yang"},"message":"ext4: don't copy non-existent gdt blocks when resizing\n\nThe resize code was copying blocks at the beginning of each block\ngroup in order to copy the superblock and block group descriptor table\n(gdt) blocks.  This was, unfortunately, being done even for block\ngroups that did not have super blocks or gdt blocks.  This is a\ncomplete waste of perfectly good I/O bandwidth, to skip writing those\nblocks for sparse bg's.\n\nSigned-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/2d1258784205073dcba111c9ca148b3711a220ab"},{"sha":"14357c80016086978588993ea9324bf66cd666ce","author":{"email":"cc47c8d45a0a3c6300393e2d0c4f6e661d0cfdb0@gmail.com","name":"Yongqiang Yang"},"message":"ext4: avoid duplicate writes of the backup bg descriptor blocks\n\nThe resize code was needlessly writing the backup block group\ndescriptor blocks multiple times (once per block group) during an\nonline resize.\n\nSigned-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/14357c80016086978588993ea9324bf66cd666ce"},{"sha":"f71963b532d0f198ea24e037b7842349570a0fde","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4: fix potential deadlock in ext4_nonda_switch()\n\nIn ext4_nonda_switch(), if the file system is getting full we used to\ncall writeback_inodes_sb_if_idle().  The problem is that we can be\nholding i_mutex already, and this causes a potential deadlock when\nwriteback_inodes_sb_if_idle() when it tries to take s_umount.  (See\nlockdep output below).\n\nAs it turns out we don't need need to hold s_umount; the fact that we\nare in the middle of the write(2) system call will keep the superblock\npinned.  Unfortunately writeback_inodes_sb() checks to make sure\ns_umount is taken, and the VFS uses a different mechanism for making\nsure the file system doesn't get unmounted out from under us.  The\nsimplest way of dealing with this is to just simply grab s_umount\nusing a trylock, and skip kicking the writeback flusher thread in the\nvery unlikely case that we can't take a read lock on s_umount without\nblocking.\n\nAlso, we now check the cirteria for kicking the writeback thread\nbefore we decide to whether to fall back to non-delayed writeback, so\nif there are any outstanding delayed allocation writes, we try to get\nthem resolved as soon as possible.\n\n   [ INFO: possible circular locking dependency detected ]\n   3.6.0-rc1-00042-gce894ca #367 Not tainted\n   -------------------------------------------------------\n   dd/8298 is trying to acquire lock:\n    (&type->s_umount_key#18){++++..}, at: [<c02277d4>] writeback_inodes_sb_if_idle+0x28/0x46\n\n   but task is already holding lock:\n    (&sb->s_type->i_mutex_key#8){+.+...}, at: [<c01ddcce>] generic_file_aio_write+0x5f/0xd3\n\n   which lock already depends on the new lock.\n\n   2 locks held by dd/8298:\n    #0:  (sb_writers#2){.+.+.+}, at: [<c01ddcc5>] generic_file_aio_write+0x56/0xd3\n    #1:  (&sb->s_type->i_mutex_key#8){+.+...}, at: [<c01ddcce>] generic_file_aio_write+0x5f/0xd3\n\n   stack backtrace:\n   Pid: 8298, comm: dd Not tainted 3.6.0-rc1-00042-gce894ca #367\n   Call Trace:\n    [<c015b79c>] ? console_unlock+0x345/0x372\n    [<c06d62a1>] print_circular_bug+0x190/0x19d\n    [<c019906c>] __lock_acquire+0x86d/0xb6c\n    [<c01999db>] ? mark_held_locks+0x5c/0x7b\n    [<c0199724>] lock_acquire+0x66/0xb9\n    [<c02277d4>] ? writeback_inodes_sb_if_idle+0x28/0x46\n    [<c06db935>] down_read+0x28/0x58\n    [<c02277d4>] ? writeback_inodes_sb_if_idle+0x28/0x46\n    [<c02277d4>] writeback_inodes_sb_if_idle+0x28/0x46\n    [<c026f3b2>] ext4_nonda_switch+0xe1/0xf4\n    [<c0271ece>] ext4_da_write_begin+0x27/0x193\n    [<c01dcdb0>] generic_file_buffered_write+0xc8/0x1bb\n    [<c01ddc47>] __generic_file_aio_write+0x1dd/0x205\n    [<c01ddce7>] generic_file_aio_write+0x78/0xd3\n    [<c026d336>] ext4_file_write+0x480/0x4a6\n    [<c0198c1d>] ? __lock_acquire+0x41e/0xb6c\n    [<c0180944>] ? sched_clock_cpu+0x11a/0x13e\n    [<c01967e9>] ? trace_hardirqs_off+0xb/0xd\n    [<c018099f>] ? local_clock+0x37/0x4e\n    [<c0209f2c>] do_sync_write+0x67/0x9d\n    [<c0209ec5>] ? wait_on_retry_sync_kiocb+0x44/0x44\n    [<c020a7b9>] vfs_write+0x7b/0xe6\n    [<c020a9a6>] sys_write+0x3b/0x64\n    [<c06dd4bd>] syscall_call+0x7/0xb\n\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/f71963b532d0f198ea24e037b7842349570a0fde"},{"sha":"9933aad93d4d45818e33768bc45ac73e61df89d2","author":{"email":"c0bea5071bf2f1175292d0efab346af8983495d1@canonical.com","name":"Herton Ronaldo Krzesinski"},"message":"ext4: fix crash when accessing /proc/mounts concurrently\n\nThe crash was caused by a variable being erronously declared static in\ntoken2str().\n\nIn addition to /proc/mounts, the problem can also be easily replicated\nby accessing /proc/fs/ext4/<partition>/options in parallel:\n\n$ cat /proc/fs/ext4/<partition>/options > options.txt\n\n... and then running the following command in two different terminals:\n\n$ while diff /proc/fs/ext4/<partition>/options options.txt; do true; done\n\nThis is also the cause of the following a crash while running xfstests\n#234, as reported in the following bug reports:\n\n\thttps://bugs.launchpad.net/bugs/1053019\n\thttps://bugzilla.kernel.org/show_bug.cgi?id=47731\n\nSigned-off-by: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nCc: Brad Figg <brad.figg@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/9933aad93d4d45818e33768bc45ac73e61df89d2"},{"sha":"b120e72c25deeb4fd9e1cd23d0c74f945ac21c8b","author":{"email":"eecfa5af1016ca9db755569d9919e212ab6a1c94@openvz.org","name":"Dmitry Monakhov"},"message":"ext4: move_extent code cleanup\n\n- Remove usless checks, because it is too late to check that inode != NULL\n  at the moment it was referenced several times.\n- Double lock routines looks very ugly and locking ordering relays on\n  order of i_ino, but other kernel code rely on order of pointers.\n  Let's make them simple and clean.\n- check that inodes belongs to the same SB as soon as possible.\n\nSigned-off-by: Dmitry Monakhov <dmonakhov@openvz.org>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/b120e72c25deeb4fd9e1cd23d0c74f945ac21c8b"},{"sha":"898b851ea005ad5b5fd9c04e9b3e6ec0c92f4b9b","author":{"email":"eecfa5af1016ca9db755569d9919e212ab6a1c94@openvz.org","name":"Dmitry Monakhov"},"message":"ext4: online defrag is not supported for journaled files\n\nProper block swap for inodes with full journaling enabled is\ntruly non obvious task. In order to be on a safe side let's\nexplicitly disable it for now.\n\nSigned-off-by: Dmitry Monakhov <dmonakhov@openvz.org>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/898b851ea005ad5b5fd9c04e9b3e6ec0c92f4b9b"},{"sha":"a562dec9ab05ce6571b8505faaaaa0ffe7d0a3ad","author":{"email":"8f3a35bc41bb68befb60350a9d66659e18d711f7@itwm.fraunhofer.de","name":"Bernd Schubert"},"message":"ext4: always set i_op in ext4_mknod()\n\next4_special_inode_operations have their own ifdef CONFIG_EXT4_FS_XATTR\nto mask those methods. And ext4_iget also always sets it, so there is\nan inconsistency.\n\nSigned-off-by: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/a562dec9ab05ce6571b8505faaaaa0ffe7d0a3ad"},{"sha":"3e333c2bbd5e24ec3b51f5cfad06e64287eca151","author":{"email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz","name":"Jan Kara"},"message":"ext4: fix fdatasync() for files with only i_size changes\n\nCode tracking when transaction needs to be committed on fdatasync(2) forgets\nto handle a situation when only inode's i_size is changed. Thus in such\nsituations fdatasync(2) doesn't force transaction with new i_size to disk\nand that can result in wrong i_size after a crash.\n\nFix the issue by updating inode's i_datasync_tid whenever its size is\nupdated.\n\nReported-by: Kristian Nielsen <knielsen@knielsen-hq.org>\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/3e333c2bbd5e24ec3b51f5cfad06e64287eca151"},{"sha":"27d1c0f4b0da19254a1ba427ac24f0dfbb39ae92","author":{"email":"eecfa5af1016ca9db755569d9919e212ab6a1c94@openvz.org","name":"Dmitry Monakhov"},"message":"ext4: race-condition protection for ext4_convert_unwritten_extents_endio\n\nWe assumed that at the time we call ext4_convert_unwritten_extents_endio()\nextent in question is fully inside [map.m_lblk, map->m_len] because\nit was already split during submission.  But this may not be true due to\na race between writeback vs fallocate.\n\nIf extent in question is larger than requested we will split it again.\nSpecial precautions should being done if zeroout required because\n[map.m_lblk, map->m_len] already contains valid data.\n\nSigned-off-by: Dmitry Monakhov <dmonakhov@openvz.org>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/27d1c0f4b0da19254a1ba427ac24f0dfbb39ae92"},{"sha":"447d1f8e058b88a664a46acb89bd030ad56952ac","author":{"email":"6c9141d0e2318b390a8a6bf8ecd9f819d16f05b4@redhat.com","name":"Lukas Czerner"},"message":"ext4: Avoid underflow in ext4_trim_fs()\n\nCurrently if len argument in ext4_trim_fs() is smaller than one block,\nthe 'end' variable underflow. Avoid that by returning EINVAL if len is\nsmaller than file system block.\n\nAlso remove useless unlikely().\n\nSigned-off-by: Lukas Czerner <lczerner@redhat.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/447d1f8e058b88a664a46acb89bd030ad56952ac"},{"sha":"77ebb3d4d1d347f19cfc12261c357e8abaaa7919","author":{"email":"34b4aa64e889ad0f038e03f54f9e4007ea592ecf@rosalab.ru","name":"Eugene Shatokhin"},"message":"ext4: fix memory leak in ext4_xattr_set_acl()'s error path\n\nIn ext4_xattr_set_acl(), if ext4_journal_start() returns an error,\nposix_acl_release() will not be called for 'acl' which may result in a\nmemory leak.\n\nThis patch fixes that.\n\nReviewed-by: Lukas Czerner <lczerner@redhat.com>\nSigned-off-by: Eugene Shatokhin <eugene.shatokhin@rosalab.ru>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/77ebb3d4d1d347f19cfc12261c357e8abaaa7919"},{"sha":"e135a29d2e466326c1b871ff0868f83c5072f3e8","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4: fix possible use after free with metadata csum\n\nCommit fa77dcfafeaa introduces block bitmap checksum calculation into\next4_new_inode() in the case that block group was uninitialized.\nHowever we brelse() the bitmap buffer before we attempt to checksum it\nso we have no guarantee that the buffer is still there.\n\nFix this by releasing the buffer after the possible checksum\ncomputation.\n\nSigned-off-by: Lukas Czerner <lczerner@redhat.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nAcked-by: Darrick J. Wong <darrick.wong@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/e135a29d2e466326c1b871ff0868f83c5072f3e8"},{"sha":"d2c50771a44b793c9c7ea7079a03b5213de90464","author":{"email":"6cba6d9ce6c4c92c9d9c53fdcd445acfec8e8f00@synology.com","name":"Forrest Liu"},"message":"ext4: fix extent tree corruption caused by hole punch\n\nWhen depth of extent tree is greater than 1, logical start value of\ninterior node is not correctly updated in ext4_ext_rm_idx.\n\nSigned-off-by: Forrest Liu <forrestl@synology.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nReviewed-by: Ashish Sangwan <ashishsangwan2@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/d2c50771a44b793c9c7ea7079a03b5213de90464"},{"sha":"0aed65c3aae15cf9ffc987b9dd6d008e3b4922df","author":{"email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz","name":"Jan Kara"},"message":"ext4: check dioread_nolock on remount\n\nCurrently we allow enabling dioread_nolock mount option on remount for\nfilesystems where blocksize < PAGE_CACHE_SIZE.  This isn't really\nsupported so fix the bug by moving the check for blocksize !=\nPAGE_CACHE_SIZE into parse_options(). Change the original PAGE_SIZE to\nPAGE_CACHE_SIZE along the way because that's what we are really\ninterested in.\n\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nReviewed-by: Eric Sandeen <sandeen@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/0aed65c3aae15cf9ffc987b9dd6d008e3b4922df"},{"sha":"03e07099598d3e2280d76046a4894a48722e64eb","author":{"email":"389bd06664b699d49ce291f515b98373073ad5f4@tls.msk.ru","name":"Michael Tokarev"},"message":"ext4: do not try to write superblock on ro remount w/o journal\n\nWhen a journal-less ext4 filesystem is mounted on a read-only block\ndevice (blockdev --setro will do), each remount (for other, unrelated,\nflags, like suid=>nosuid etc) results in a series of scary messages\nfrom kernel telling about I/O errors on the device.\n\nThis is becauese of the following code ext4_remount():\n\n       if (sbi->s_journal == NULL)\n                ext4_commit_super(sb, 1);\n\nat the end of remount procedure, which forces writing (flushing) of\na superblock regardless whenever it is dirty or not, if the filesystem\nis readonly or not, and whenever the device itself is readonly or not.\n\nWe only need call ext4_commit_super when the file system had been\npreviously mounted read/write.\n\nThanks to Eric Sandeen for help in diagnosing this issue.\n\nSigned-off-By: Michael Tokarev <mjt@tls.msk.ru>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/03e07099598d3e2280d76046a4894a48722e64eb"},{"sha":"b3bba48ce1e0f3e39d25e0de3a20310179fd8180","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4: lock i_mutex when truncating orphan inodes\n\nCommit c278531d39 added a warning when ext4_flush_unwritten_io() is\ncalled without i_mutex being taken.  It had previously not been taken\nduring orphan cleanup since races weren't possible at that point in\nthe mount process, but as a result of this c278531d39, we will now see\na kernel WARN_ON in this case.  Take the i_mutex in\next4_orphan_cleanup() to suppress this warning.\n\nReported-by: Alexander Beregalov <a.beregalov@gmail.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nReviewed-by: Zheng Liu <wenqing.lz@taobao.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Stefanescu Cristian <howerkraft@gmail.com>","distinct":true,"url":"https://api.github.com/repos/StefanescuCristian/hammerhead/commits/b3bba48ce1e0f3e39d25e0de3a20310179fd8180"}]}