[v5.15] kernel BUG in ocfs2_commit_truncate

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3b8db0e4f263 Linux 5.15.182
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=104b6e70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=dd5e00a2e31fafd7
dashboard link: https://syzkaller.appspot.com/bug?extid=52a632ca38a402603b04
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ff1afedf7b4d/disk-3b8db0e4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19cb045784cf/vmlinux-3b8db0e4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/43c663d2f6a5/Image-3b8db0e4.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+52a632...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/ocfs2/alloc.c:686!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4930 Comm: syz-executor Not tainted 5.15.182-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_new_path fs/ocfs2/alloc.c:686 [inline]
pc : ocfs2_commit_truncate+0x17c8/0x17fc fs/ocfs2/alloc.c:7228
lr : ocfs2_new_path fs/ocfs2/alloc.c:686 [inline]
lr : ocfs2_commit_truncate+0x17c8/0x17fc fs/ocfs2/alloc.c:7228
sp : ffff800020a26fe0
x29: ffff800020a272a0 x28: ffff0000d9a88000 x27: ffff0000efc642c0
x26: dfff800000000000 x25: ffff700004144e14 x24: 0000000000001fff
x23: 000000000000000d x22: 1fffe0001df8c858 x21: ffff800009c7d7ac
x20: 0000000000000138 x19: ffff0000f0867828 x18: 0000000000000000
x17: ffff800016cdf000 x16: ffff8000082bdde4 x15: ffff80000891c220
x14: ffff80000891afdc x13: ffff80000805ac1c x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff800009bf67f0
x8 : ffff0000d1923680 x7 : 0000000000000000 x6 : ffff80000805b058
x5 : ffff0000e7eaffe8 x4 : 0000000000000000 x3 : 0000000000000010
x2 : 0000000000000000 x1 : 0000000000000138 x0 : 0000000000000004
Call trace:
ocfs2_new_path fs/ocfs2/alloc.c:686 [inline]
ocfs2_commit_truncate+0x17c8/0x17fc fs/ocfs2/alloc.c:7228
ocfs2_truncate_for_delete fs/ocfs2/inode.c:623 [inline]
ocfs2_wipe_inode fs/ocfs2/inode.c:790 [inline]
ocfs2_delete_inode fs/ocfs2/inode.c:1079 [inline]
ocfs2_evict_inode+0xd28/0x395c fs/ocfs2/inode.c:1216
evict+0x3c8/0x810 fs/inode.c:647
iput_final fs/inode.c:1769 [inline]
iput+0x6c4/0x77c fs/inode.c:1795
d_delete_notify include/linux/fsnotify.h:267 [inline]
vfs_rmdir+0x2f4/0x3ec fs/namei.c:4162
do_rmdir+0x240/0x634 fs/namei.c:4210
__do_sys_unlinkat fs/namei.c:4390 [inline]
__se_sys_unlinkat fs/namei.c:4384 [inline]
__arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4384
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: aa1403e0 97b156da 17fffeda 97a20840 (d4210000)
---[ end trace d770a958f036ee99 ]---


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.