[syzbot] [ocfs2?] kernel BUG in ocfs2_xattr_value_truncate (2)

[syzbot <syzbot+e538032956b1157914a3@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    2961f841b025 Merge tag 'turbostat-2026.02.14' of git://git..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10e3bee6580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=65722f41f7edc17e
dashboard link: https://syzkaller.appspot.com/bug?extid=e538032956b1157914a3
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-2961f841.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19ffd1a88c42/vmlinux-2961f841.xz
kernel image: https://storage.googleapis.com/syzbot-assets/621dc0fadd96/bzImage-2961f841.xz

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

loop0: detected capacity change from 32768 to 0
------------[ cut here ]------------
kernel BUG at fs/ocfs2/xattr.c:747!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5327 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:ocfs2_xattr_extend_allocation fs/ocfs2/xattr.c:747 [inline]
RIP: 0010:ocfs2_xattr_value_truncate+0x178b/0x1790 fs/ocfs2/xattr.c:868
Code: 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 51 eb ff ff 4c 89 ff 48 89 f3 e8 03 4e 5d fe 48 89 de e9 3e eb ff ff e8 66 b4 f1 fd 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3
RSP: 0018:ffffc9000f64e920 EFLAGS: 00010287
RAX: ffffffff83d3e31a RBX: 0000000000000002 RCX: 0000000000100000
RDX: ffffc90020802000 RSI: 0000000000001a65 RDI: 0000000000001a66
RBP: ffffc9000f64ec50 R08: ffff888035132480 R09: 0000000000000006
R10: 00000000fffffffc R11: 0000000000000002 R12: 0000000000000002
R13: 00000000fffffff5 R14: 0000000000000000 R15: ffff888056fa93d0
FS:  00007f0d56df56c0(0000) GS:ffff88808ca5b000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000491000 CR3: 000000001fc51000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 ocfs2_xa_value_truncate+0x2a5/0x3f0 fs/ocfs2/xattr.c:1945
 ocfs2_xa_prepare_entry fs/ocfs2/xattr.c:2204 [inline]
 ocfs2_xa_set+0x238e/0x2ec0 fs/ocfs2/xattr.c:2282
 ocfs2_xattr_block_set+0x3e0/0x3480 fs/ocfs2/xattr.c:3016
 __ocfs2_xattr_set_handle+0x6b3/0xf50 fs/ocfs2/xattr.c:3418
 ocfs2_xattr_set+0xf3f/0x13e0 fs/ocfs2/xattr.c:3681
 __vfs_setxattr+0x43c/0x480 fs/xattr.c:200
 __vfs_setxattr_noperm+0x12d/0x660 fs/xattr.c:234
 vfs_setxattr+0x163/0x360 fs/xattr.c:321
 do_setxattr fs/xattr.c:636 [inline]
 filename_setxattr+0x296/0x630 fs/xattr.c:664
 path_setxattrat+0x3eb/0x440 fs/xattr.c:708
 __do_sys_lsetxattr fs/xattr.c:749 [inline]
 __se_sys_lsetxattr fs/xattr.c:745 [inline]
 __x64_sys_lsetxattr+0xbf/0xe0 fs/xattr.c:745
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0d5a99c629
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:00007f0d56df5028 EFLAGS: 00000246 ORIG_RAX: 00000000000000bd
RAX: ffffffffffffffda RBX: 00007f0d5ac16180 RCX: 00007f0d5a99c629
RDX: 0000200000000480 RSI: 00002000000000c0 RDI: 0000200000000100
RBP: 00007f0d5aa32b39 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000fe37 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0d5ac16218 R14: 00007f0d5ac16180 R15: 00007ffd722eb838
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_xattr_extend_allocation fs/ocfs2/xattr.c:747 [inline]
RIP: 0010:ocfs2_xattr_value_truncate+0x178b/0x1790 fs/ocfs2/xattr.c:868
Code: 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 51 eb ff ff 4c 89 ff 48 89 f3 e8 03 4e 5d fe 48 89 de e9 3e eb ff ff e8 66 b4 f1 fd 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3
RSP: 0018:ffffc9000f64e920 EFLAGS: 00010287
RAX: ffffffff83d3e31a RBX: 0000000000000002 RCX: 0000000000100000
RDX: ffffc90020802000 RSI: 0000000000001a65 RDI: 0000000000001a66
RBP: ffffc9000f64ec50 R08: ffff888035132480 R09: 0000000000000006
R10: 00000000fffffffc R11: 0000000000000002 R12: 0000000000000002
R13: 00000000fffffff5 R14: 0000000000000000 R15: ffff888056fa93d0
FS:  00007f0d56df56c0(0000) GS:ffff88808ca5b000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0d565d1ff8 CR3: 000000001fc51000 CR4: 0000000000352ef0


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