[v6.1] kernel BUG in ocfs2_truncate_file (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 090666d3cc90 Linux 6.1.177
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=141fe346580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5aae664b2df43c2
dashboard link: https://syzkaller.appspot.com/bug?extid=5ca287559ef421a50d37
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0b218516a5e9/disk-090666d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3239ad568bdf/vmlinux-090666d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8b19cfbec3e/bzImage-090666d3.xz

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

(syz.0.1,4404,1):ocfs2_truncate_file:456 ERROR: Inode 17058, inode i_size = 0 != di i_size = 422212465065984, i_flags = 0x6a517b06
------------[ cut here ]------------
kernel BUG at fs/ocfs2/file.c:456!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 4404 Comm: syz.0.1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:ocfs2_truncate_file+0x1416/0x1660 fs/ocfs2/file.c:450
Code: 00 54 cc 8a 49 89 d8 4d 89 f1 50 41 54 e8 a2 cf 15 00 48 83 c4 10 48 b8 00 00 00 00 00 fc ff df 48 8b 4c 24 10 c6 44 01 18 f8 <0f> 0b 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 48 f8 ff ff 48 89 df e8
RSP: 0018:ffffc900043c7340 EFLAGS: 00010282
RAX: dffffc0000000000 RBX: 00000000000042a2 RCX: 1ffff92000878e78
RDX: ffffc9000f305000 RSI: 00000000000245c6 RDI: 00000000000245c7
RBP: ffffc900043c7570 R08: ffffc900043c6ec7 R09: 1ffff92000878dd8
R10: dffffc0000000000 R11: fffff52000878dd9 R12: 0001800000000000
R13: ffff88807011d42c R14: 0000000000000000 R15: ffffc900043c7480
FS: 00007fddae4426c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdffa93f000 CR3: 00000000243cf000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ocfs2_setattr+0x16f8/0x1d90 fs/ocfs2/file.c:1212
notify_change+0xca0/0xf90 fs/attr.c:499
do_truncate+0x1ac/0x240 fs/open.c:65
handle_truncate fs/namei.c:3293 [inline]
do_open fs/namei.c:3638 [inline]
path_openat+0x2897/0x2f10 fs/namei.c:3791
do_filp_open+0x1ee/0x420 fs/namei.c:3818
do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
do_sys_open fs/open.c:1336 [inline]
__do_sys_open fs/open.c:1344 [inline]
__se_sys_open fs/open.c:1340 [inline]
__x64_sys_open+0x11b/0x140 fs/open.c:1340
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fddad59de59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fddae442028 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007fddad826090 RCX: 00007fddad59de59
RDX: 0000000000000000 RSI: 000000000014927e RDI: 0000200000000180
RBP: 00007fddad633e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fddad826128 R14: 00007fddad826090 R15: 00007ffc99527188
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_truncate_file+0x1416/0x1660 fs/ocfs2/file.c:450
Code: 00 54 cc 8a 49 89 d8 4d 89 f1 50 41 54 e8 a2 cf 15 00 48 83 c4 10 48 b8 00 00 00 00 00 fc ff df 48 8b 4c 24 10 c6 44 01 18 f8 <0f> 0b 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 48 f8 ff ff 48 89 df e8
RSP: 0018:ffffc900043c7340 EFLAGS: 00010282
RAX: dffffc0000000000 RBX: 00000000000042a2 RCX: 1ffff92000878e78
RDX: ffffc9000f305000 RSI: 00000000000245c6 RDI: 00000000000245c7
RBP: ffffc900043c7570 R08: ffffc900043c6ec7 R09: 1ffff92000878dd8
R10: dffffc0000000000 R11: fffff52000878dd9 R12: 0001800000000000
R13: ffff88807011d42c R14: 0000000000000000 R15: ffffc900043c7480
FS: 00007fddae4426c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdffa946000 CR3: 00000000243cf000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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