[syzbot] [ext4?] WARNING in jbd2_journal_dirty_metadata

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    b31c44928842 Merge tag 'linux_kselftest-kunit-fixes-6.11-r..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10d28600580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=58a85aa6925a8b78
dashboard link: https://syzkaller.appspot.com/bug?extid=5cdc66c11e7bf43a9931
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-b31c4492.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c7a83e0168a1/vmlinux-b31c4492.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f991c4e68b58/bzImage-b31c4492.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5cdc66c11e7bf43a9931@xxxxxxxxxxxxxxxxxxxxxxxxx

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5119 at fs/jbd2/transaction.c:1556 jbd2_journal_dirty_metadata+0x8b2/0xc00 fs/jbd2/transaction.c:1556
Modules linked in:
CPU: 0 UID: 0 PID: 5119 Comm: syz.0.0 Not tainted 6.11.0-rc6-syzkaller-00308-gb31c44928842 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:jbd2_journal_dirty_metadata+0x8b2/0xc00 fs/jbd2/transaction.c:1556
Code: 8b 44 24 08 49 89 e9 50 41 55 53 41 57 e8 96 fc 45 09 48 83 c4 20 90 0f 0b 90 bb ea ff ff ff e9 26 fe ff ff e8 6f df 22 ff 90 <0f> 0b 90 bb e4 ff ff ff e9 13 fe ff ff 89 d9 80 e1 07 80 c1 03 38
RSP: 0018:ffffc90002e1e798 EFLAGS: 00010283
RAX: ffffffff8270ad41 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc9000b77b000 RSI: 00000000000221a7 RDI: 00000000000221a8
RBP: 1ffff11007b37edc R08: ffffffff8270a96a R09: fffff520005c3ce4
R10: dffffc0000000000 R11: fffff520005c3ce4 R12: dffffc0000000000
R13: ffff8880419c0e80 R14: 1ffff110083381d0 R15: ffff88803d9bf690
FS:  00007f0458bdb6c0(0000) GS:ffff88801fe00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000201da000 CR3: 000000001feaa000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ocfs2_journal_dirty+0x156/0x7c0 fs/ocfs2/journal.c:812
 ocfs2_add_branch fs/ocfs2/alloc.c:1325 [inline]
 ocfs2_grow_tree+0x2761/0x37d0 fs/ocfs2/alloc.c:1585
 ocfs2_split_and_insert+0x421/0x1690 fs/ocfs2/alloc.c:4943
 ocfs2_split_extent+0x1319/0x2020 fs/ocfs2/alloc.c:5125
 ocfs2_change_extent_flag+0xa70/0xda0 fs/ocfs2/alloc.c:5222
 ocfs2_mark_extent_refcounted fs/ocfs2/refcounttree.c:2354 [inline]
 ocfs2_add_refcount_flag+0x89b/0x1150 fs/ocfs2/refcounttree.c:3701
 ocfs2_reflink_remap_extent fs/ocfs2/refcounttree.c:4542 [inline]
 ocfs2_reflink_remap_blocks+0xe58/0x1f30 fs/ocfs2/refcounttree.c:4669
 ocfs2_remap_file_range+0x600/0x8e0 fs/ocfs2/file.c:2724
 vfs_copy_file_range+0xc1f/0x1530 fs/read_write.c:1522
 __do_sys_copy_file_range fs/read_write.c:1612 [inline]
 __se_sys_copy_file_range+0x3f2/0x5d0 fs/read_write.c:1575
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0457d7cef9
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:00007f0458bdb038 EFLAGS: 00000246 ORIG_RAX: 0000000000000146
RAX: ffffffffffffffda RBX: 00007f0457f36058 RCX: 00007f0457d7cef9
RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f0457def046 R08: 0000000000002fff R09: 0000000000000000
R10: 0000000020000640 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f0457f36058 R15: 00007ffff37854b8
 </TASK>


---
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@xxxxxxxxxxxxxxxx.

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