summaryrefslogtreecommitdiffstats
path: root/fs/jbd2
diff options
context:
space:
mode:
authorBaokun Li <libaokun1@huawei.com>2023-01-07 11:21:26 +0800
committerTheodore Ts'o <tytso@mit.edu>2023-02-19 00:09:59 -0500
commit3039d8b8692408438a618fac2776b629852663c3 (patch)
tree0a5ecb12895f89ed755e48f90a8ff0f3e2f39802 /fs/jbd2
parent5cd740287ae5e3f9d1c46f5bfe8778972fd6d3fe (diff)
downloadlinux-3039d8b8692408438a618fac2776b629852663c3.tar.gz
linux-3039d8b8692408438a618fac2776b629852663c3.tar.bz2
linux-3039d8b8692408438a618fac2776b629852663c3.zip
ext4: update s_journal_inum if it changes after journal replay
When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the journal through the old s_journal_inum. And the new s_journal_inum bypasses some of the checks in ext4_get_journal(), which may trigger a null pointer dereference problem. So if s_journal_inum changes after the journal replay, we ignore the change, and rewrite the current journal_inum to the superblock. Link: https://bugzilla.kernel.org/show_bug.cgi?id=216541 Reported-by: Luís Henriques <lhenriques@suse.de> Signed-off-by: Baokun Li <libaokun1@huawei.com> Reviewed-by: Jan Kara <jack@suse.cz> Link: https://lore.kernel.org/r/20230107032126.4165860-3-libaokun1@huawei.com Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/jbd2')
0 files changed, 0 insertions, 0 deletions