[v6.6] kernel BUG in jbd2_journal_dirty_metadata

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: da47cbc25466 Linux 6.6.144
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11068789580000
kernel config: https://syzkaller.appspot.com/x/.config?x=938110aa66424b94
dashboard link: https://syzkaller.appspot.com/bug?extid=8236fc14102a4694f23a
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/a9e82134d7e6/disk-da47cbc2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/296a86743157/vmlinux-da47cbc2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c5adb532f254/bzImage-da47cbc2.xz

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

(syz.3.173,6647,0):ocfs2_xattr_shrink_size:836 ERROR: status = -30
(syz.3.173,6647,0):__ocfs2_journal_access:727 ERROR: Error -30 getting 1 access to buffer!
(syz.3.173,6647,0):ocfs2_xa_prepare_entry:2151 ERROR: status = -30
(syz.3.173,6647,0):ocfs2_xa_set:2254 ERROR: status = -30
------------[ cut here ]------------
kernel BUG at fs/jbd2/transaction.c:1508!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 6647 Comm: syz.3.173 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026
RIP: 0010:jbd2_journal_dirty_metadata+0xca5/0xd70 fs/jbd2/transaction.c:1507
Code: ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c cb fb ff ff 48 89 df 48 89 d5 e8 d8 f4 96 ff 48 89 ea e9 b8 fb ff ff e8 0b 7d 3e ff <0f> 0b 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 4d fc ff ff 48 89 df e8
RSP: 0018:ffffc900045ded10 EFLAGS: 00010287
RAX: ffffffff82486865 RBX: ffff8880308f4250 RCX: 0000000000080000
RDX: ffffc9000db3d000 RSI: 0000000000015b68 RDI: 0000000000015b69
RBP: 1ffff1100610d5b8 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff520008bbd90 R12: 1ffff1100611e849
R13: 1ffff1100d7b9c1d R14: ffff88806bdce0e8 R15: 1ffff1100611e84a
FS: 00007fbc1ac686c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f59f45d4ff8 CR3: 000000007b669000 CR4: 00000000003506f0
Call Trace:
<TASK>
ocfs2_journal_dirty+0x12e/0x6c0 fs/ocfs2/journal.c:834
ocfs2_xa_journal_dirty fs/ocfs2/xattr.c:1453 [inline]
ocfs2_xa_set+0x15a1/0x2e40 fs/ocfs2/xattr.c:2263
ocfs2_xattr_block_set+0x3c7/0x2dc0 fs/ocfs2/xattr.c:2985
__ocfs2_xattr_set_handle+0x6b9/0xf30 fs/ocfs2/xattr.c:3387
ocfs2_xattr_set+0xf1c/0x13a0 fs/ocfs2/xattr.c:3650
__vfs_setxattr+0x437/0x470 fs/xattr.c:201
__vfs_setxattr_noperm+0x12a/0x5e0 fs/xattr.c:235
vfs_setxattr+0x16b/0x2f0 fs/xattr.c:322
do_setxattr fs/xattr.c:630 [inline]
path_setxattr+0x33a/0x590 fs/xattr.c:659
__do_sys_setxattr fs/xattr.c:677 [inline]
__se_sys_setxattr fs/xattr.c:673 [inline]
__x64_sys_setxattr+0xbb/0xd0 fs/xattr.c:673
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fbc19d9de59
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:00007fbc1ac68028 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fbc1a025fa0 RCX: 00007fbc19d9de59
RDX: 0000000000000000 RSI: 0000200000000200 RDI: 00002000000000c0
RBP: 00007fbc19e33e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fbc1a026038 R14: 00007fbc1a025fa0 R15: 00007ffd7d397bf8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:jbd2_journal_dirty_metadata+0xca5/0xd70 fs/jbd2/transaction.c:1507
Code: ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c cb fb ff ff 48 89 df 48 89 d5 e8 d8 f4 96 ff 48 89 ea e9 b8 fb ff ff e8 0b 7d 3e ff <0f> 0b 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 4d fc ff ff 48 89 df e8
RSP: 0018:ffffc900045ded10 EFLAGS: 00010287
RAX: ffffffff82486865 RBX: ffff8880308f4250 RCX: 0000000000080000
RDX: ffffc9000db3d000 RSI: 0000000000015b68 RDI: 0000000000015b69
RBP: 1ffff1100610d5b8 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff520008bbd90 R12: 1ffff1100611e849
R13: 1ffff1100d7b9c1d R14: ffff88806bdce0e8 R15: 1ffff1100611e84a
FS: 00007fbc1ac686c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f59f45d4ff8 CR3: 000000007b669000 CR4: 00000000003506f0


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