diff options
| author | Jan Kara <jack@suse.cz> | 2021-05-03 11:39:03 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-09-22 11:47:49 +0200 |
| commit | dd6ab4e1c2b6a22318f2526282dbf33c7fb51151 (patch) | |
| tree | bf0ef7d2dc3d051f573df3c1f3f94de8c3aee221 /fs/ext4 | |
| parent | e6c3fefc6bb11bef1bd8adfe37e0f317303ab751 (diff) | |
| download | linux-stable-dd6ab4e1c2b6a22318f2526282dbf33c7fb51151.tar.gz linux-stable-dd6ab4e1c2b6a22318f2526282dbf33c7fb51151.tar.bz2 linux-stable-dd6ab4e1c2b6a22318f2526282dbf33c7fb51151.zip | |
udf: Check LVID earlier
[ Upstream commit 781d2a9a2fc7d0be53a072794dc03ef6de770f3d ]
We were checking validity of LVID entries only when getting
implementation use information from LVID in udf_sb_lvidiu(). However if
the LVID is suitably corrupted, it can cause problems also to code such
as udf_count_free() which doesn't use udf_sb_lvidiu(). So check validity
of LVID already when loading it from the disk and just disable LVID
altogether when it is not valid.
Reported-by: syzbot+7fbfe5fed73ebb675748@syzkaller.appspotmail.com
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/ext4')
0 files changed, 0 insertions, 0 deletions