summaryrefslogtreecommitdiffstats
path: root/tools/vm
diff options
context:
space:
mode:
authorluojiajun <luojiajun3@huawei.com>2019-03-01 00:30:00 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-04-05 22:33:00 +0200
commit6a817a7aed1c4074274118d6a27f8b094e2fe0dd (patch)
tree4af3d4c73c710a97d8a8fa709e5bad5868328173 /tools/vm
parentca66f667189c39b9128c1fba5d0be23d933009d9 (diff)
downloadlinux-stable-6a817a7aed1c4074274118d6a27f8b094e2fe0dd.tar.gz
linux-stable-6a817a7aed1c4074274118d6a27f8b094e2fe0dd.tar.bz2
linux-stable-6a817a7aed1c4074274118d6a27f8b094e2fe0dd.zip
jbd2: fix invalid descriptor block checksum
[ Upstream commit 6e876c3dd205d30b0db6850e97a03d75457df007 ] In jbd2_journal_commit_transaction(), if we are in abort mode, we may flush the buffer without setting descriptor block checksum by goto start_journal_io. Then fs is mounted, jbd2_descriptor_block_csum_verify() failed. [ 271.379811] EXT4-fs (vdd): shut down requested (2) [ 271.381827] Aborting journal on device vdd-8. [ 271.597136] JBD2: Invalid checksum recovering block 22199 in log [ 271.598023] JBD2: recovery failed [ 271.598484] EXT4-fs (vdd): error loading journal Fix this problem by keep setting descriptor block checksum if the descriptor buffer is not NULL. This checksum problem can be reproduced by xfstests generic/388. Signed-off-by: luojiajun <luojiajun3@huawei.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/vm')
0 files changed, 0 insertions, 0 deletions