diff options
author | Jan Kara <jack@suse.com> | 2016-02-19 00:18:25 -0500 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2016-02-19 00:18:25 -0500 |
commit | ed8ad83808f009ade97ebbf6519bc3a97fefbc0c (patch) | |
tree | 02befbe2dee42bf5a4b7a141888d43a6ecde7469 /CREDITS | |
parent | c906f38e8853cfd407b30d2f4756a93c1d8f698f (diff) | |
download | linux-stable-ed8ad83808f009ade97ebbf6519bc3a97fefbc0c.tar.gz linux-stable-ed8ad83808f009ade97ebbf6519bc3a97fefbc0c.tar.bz2 linux-stable-ed8ad83808f009ade97ebbf6519bc3a97fefbc0c.zip |
ext4: fix bh->b_state corruption
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>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions