summaryrefslogtreecommitdiff
path: root/include/asm-powerpc/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorhongao <hongao@uniontech.com>2026-03-24 09:58:15 +0800
committerTheodore Ts'o <tytso@mit.edu>2026-03-27 23:38:52 -0400
commit3ceda17325fc2600f66fd85b526592bc8a9dfb9d (patch)
tree0bf935fc70f7c476ec10f361d85d0d49541c7c33 /include/asm-powerpc/git@git.tavy.me:linux.git
parentec0a7500d8eace5b4f305fa0c594dd148f0e8d29 (diff)
ext4: skip split extent recovery on corruption
ext4_split_extent_at() retries after ext4_ext_insert_extent() fails by refinding the original extent and restoring its length. That recovery is only safe for transient resource failures such as -ENOSPC, -EDQUOT, and -ENOMEM. When ext4_ext_insert_extent() fails because the extent tree is already corrupted, ext4_find_extent() can return a leaf path without p_ext. ext4_split_extent_at() then dereferences path[depth].p_ext while trying to fix up the original extent length, causing a NULL pointer dereference while handling a pre-existing filesystem corruption. Do not enter the recovery path for corruption errors, and validate p_ext after refinding the extent before touching it. This keeps the recovery path limited to cases it can actually repair and turns the syzbot-triggered crash into a proper corruption report. Fixes: 716b9c23b862 ("ext4: refactor split and convert extents") Reported-by: syzbot+1ffa5d865557e51cb604@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=1ffa5d865557e51cb604 Reviewed-by: Jan Kara <jack@suse.cz> Reviewed-by: Zhang Yi <yi.zhang@huawei.com> Signed-off-by: hongao <hongao@uniontech.com> Link: https://patch.msgid.link/EF77870F23FF9C90+20260324015815.35248-1-hongao@uniontech.com Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: stable@kernel.org
Diffstat (limited to 'include/asm-powerpc/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions