]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ext4: fix bh->b_state corruption
authorJan Kara <jack@suse.com>
Fri, 19 Feb 2016 05:18:25 +0000 (00:18 -0500)
committerSasha Levin <sasha.levin@oracle.com>
Tue, 12 Apr 2016 02:44:21 +0000 (22:44 -0400)
commita7635d6a0849007d2192bc02c038cc1b9d91b274
tree39455f6dfa6af12b1c47c3476aa33a2a9b45b462
parent0e3029cfab4a7884b32e1b2d3c19c12eded9804a
ext4: fix bh->b_state corruption

[ Upstream commit ed8ad83808f009ade97ebbf6519bc3a97fefbc0c ]

ext4 can update bh->b_state non-atomically in _ext4_get_block() and
ext4_da_get_block_prep(). Usually this is fine since bh is just a
temporary storage for mapping information on stack but in some cases it
can be fully living bh attached to a page. In such case non-atomic
update of bh->b_state can race with an atomic update which then gets
lost. Usually when we are mapping bh and thus updating bh->b_state
non-atomically, nobody else touches the bh and so things work out fine
but there is one case to especially worry about: ext4_finish_bio() uses
BH_Uptodate_Lock on the first bh in the page to synchronize handling of
PageWriteback state. So when blocksize < pagesize, we can be atomically
modifying bh->b_state of a buffer that actually isn't under IO and thus
can race e.g. with delalloc trying to map that buffer. The result is
that we can mistakenly set / clear BH_Uptodate_Lock bit resulting in the
corruption of PageWriteback state or missed unlock of BH_Uptodate_Lock.

Fix the problem by always updating bh->b_state bits atomically.

CC: stable@vger.kernel.org
Reported-by: Nikolay Borisov <kernel@kyup.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
fs/ext4/inode.c