]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ext4: don't allow overlapping system zones
authorJan Kara <jack@suse.cz>
Tue, 28 Jul 2020 13:04:33 +0000 (15:04 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 26 Aug 2020 09:42:14 +0000 (11:42 +0200)
commitb7507343c29e02b38bb792cdd28730957b9580dc
treee6eae4267378905ddf29df431622a8eb29a30a1f
parentcad79cf4ede41606f845567db469655185c392f4
ext4: don't allow overlapping system zones

[ Upstream commit bf9a379d0980e7413d94cb18dac73db2bfc5f470 ]

Currently, add_system_zone() just silently merges two added system zones
that overlap. However the overlap should not happen and it generally
suggests that some unrelated metadata overlap which indicates the fs is
corrupted. We should have caught such problems earlier (e.g. in
ext4_check_descriptors()) but add this check as another line of defense.
In later patch we also use this for stricter checking of journal inode
extent tree.

Reviewed-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Link: https://lore.kernel.org/r/20200728130437.7804-3-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/ext4/block_validity.c