summaryrefslogtreecommitdiffstats
path: root/fs/proc/cmdline.c
diff options
context:
space:
mode:
authorLukas Czerner <lczerner@redhat.com>2015-06-08 17:18:52 +0200
committerTheodore Ts'o <tytso@mit.edu>2015-06-08 17:18:52 +0200
commit41e5b7ed3e9597ccc46b6affc81872e6370936d9 (patch)
treed431ec519ef7a3735a65cc69d4722693735e8799 /fs/proc/cmdline.c
parentjbd2: revert must-not-fail allocation loops back to GFP_NOFAIL (diff)
downloadlinux-41e5b7ed3e9597ccc46b6affc81872e6370936d9.tar.xz
linux-41e5b7ed3e9597ccc46b6affc81872e6370936d9.zip
ext4: verify block bitmap even after fresh initialization
If we want to rely on the buffer_verified() flag of the block bitmap buffer, we have to set it consistently. However currently if we're initializing uninitialized block bitmap in ext4_read_block_bitmap_nowait() we're not going to set buffer verified at all. We can do this by simply setting the flag on the buffer, but I think it's actually better to run ext4_validate_block_bitmap() to make sure that what we did in the ext4_init_block_bitmap() is right. So run ext4_validate_block_bitmap() even after the block bitmap initialization. Also bail out early from ext4_validate_block_bitmap() if we see corrupt bitmap, since we already know it's corrupt and we do not need to verify that. Signed-off-by: Lukas Czerner <lczerner@redhat.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/proc/cmdline.c')
0 files changed, 0 insertions, 0 deletions