[v6.1] kernel BUG in ocfs2_truncate_file

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3594f306da12 Linux 6.1.147
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=151c02f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=30b8ca4950f83e04
dashboard link: https://syzkaller.appspot.com/bug?extid=8e188523131f22b94afd
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5b0395e2ec6c/disk-3594f306.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c3ec331b7d5b/vmlinux-3594f306.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bff42068e062/bzImage-3594f306.xz

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

(syz.5.46,4780,1):ocfs2_truncate_file:456 ERROR: Inode 17059, inode i_size = 38639 != di i_size = 150, i_flags = 0x8c000000
------------[ cut here ]------------
kernel BUG at fs/ocfs2/file.c:456!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4780 Comm: syz.5.46 Not tainted 6.1.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:ocfs2_truncate_file+0x128a/0x14d0 fs/ocfs2/file.c:450
Code: 45 00 4c 89 f7 48 c7 c6 5b d6 51 8c ba c8 01 00 00 48 c7 c1 c0 10 cc 8a 49 89 d8 4d 89 f9 50 41 54 e8 9a 2d 15 00 48 83 c4 10 <0f> 0b 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c ef f8 ff ff 48 89 df e8
RSP: 0018:ffffc90003887340 EFLAGS: 00010282
RAX: 0a665bcf20136b00 RBX: 00000000000042a3 RCX: 0a665bcf20136b00
RDX: ffffc9001c7b5000 RSI: 000000000005fb25 RDI: 000000000005fb26
RBP: ffffc90003887570 R08: dffffc0000000000 R09: fffff52000710dd9
R10: fffff52000710dd9 R11: 1ffff92000710dd8 R12: 0000000000000096
R13: ffff8880526e162c R14: ffffc90003887480 R15: 00000000000096ef
FS: 00007fb6e29af6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb8f4be3000 CR3: 0000000070e79000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ocfs2_setattr+0x16a9/0x1cf0 fs/ocfs2/file.c:1212
notify_change+0xc74/0xf40 fs/attr.c:499
do_truncate+0x197/0x220 fs/open.c:65
handle_truncate fs/namei.c:3285 [inline]
do_open fs/namei.c:3630 [inline]
path_openat+0x27f2/0x2e70 fs/namei.c:3783
do_filp_open+0x1c1/0x3c0 fs/namei.c:3810
do_sys_openat2+0x142/0x490 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_creat fs/open.c:1412 [inline]
__se_sys_creat fs/open.c:1406 [inline]
__x64_sys_creat+0x8c/0xb0 fs/open.c:1406
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb6e1b8eb69
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb6e29af038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007fb6e1db6080 RCX: 00007fb6e1b8eb69
RDX: 0000000000000000 RSI: 000000000000000d RDI: 0000200000000240
RBP: 00007fb6e1c11df1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fb6e1db6080 R15: 00007ffd1272a358
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_truncate_file+0x128a/0x14d0 fs/ocfs2/file.c:450
Code: 45 00 4c 89 f7 48 c7 c6 5b d6 51 8c ba c8 01 00 00 48 c7 c1 c0 10 cc 8a 49 89 d8 4d 89 f9 50 41 54 e8 9a 2d 15 00 48 83 c4 10 <0f> 0b 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c ef f8 ff ff 48 89 df e8
RSP: 0018:ffffc90003887340 EFLAGS: 00010282
RAX: 0a665bcf20136b00 RBX: 00000000000042a3 RCX: 0a665bcf20136b00
RDX: ffffc9001c7b5000 RSI: 000000000005fb25 RDI: 000000000005fb26
RBP: ffffc90003887570 R08: dffffc0000000000 R09: fffff52000710dd9
R10: fffff52000710dd9 R11: 1ffff92000710dd8 R12: 0000000000000096
R13: ffff8880526e162c R14: ffffc90003887480 R15: 00000000000096ef
FS: 00007fb6e29af6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb8f4be3000 CR3: 0000000070e79000 CR4: 00000000003506f0
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

[syzbot]

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