[v6.1] WARNING in cleanup_transaction

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1321ab403b38 Linux 6.1.45
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1094569ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5afeea223ff7d6fa
dashboard link: https://syzkaller.appspot.com/bug?extid=0fcc68327b1efc17491a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=109236ada80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14247b69a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df0f614deffc/disk-1321ab40.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/df0f1be30831/vmlinux-1321ab40.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e190f335ac9/bzImage-1321ab40.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d51536af7e47/mount_0.gz

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

BTRFS warning (device loop0): Skipping commit of aborted transaction.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 33 at fs/btrfs/transaction.c:1964 cleanup_transaction+0x70c/0x7f0 fs/btrfs/transaction.c:1964
Modules linked in:
CPU: 0 PID: 33 Comm: kworker/u4:2 Not tainted 6.1.45-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: events_unbound btrfs_async_reclaim_metadata_space
RIP: 0010:cleanup_transaction+0x70c/0x7f0 fs/btrfs/transaction.c:1964
Code: 43 04 fe 0f 0b 43 80 7c 25 00 00 0f 85 3d fa ff ff e9 40 fa ff ff e8 d3 43 04 fe 48 c7 c7 40 96 2d 8b 44 89 f6 e8 34 a1 cc fd <0f> 0b e9 91 fa ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c e9 f9 ff
RSP: 0018:ffffc90000aa7660 EFLAGS: 00010246
RAX: 7f5b51a9f1739900 RBX: 0000000000000000 RCX: ffff8880152c1dc0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90000aa7790 R08: ffffffff81525dfe R09: ffffed1017304f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100df08d84 R14: 00000000ffffffe4 R15: ffff88806f846c20
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8ba6e13010 CR3: 0000000076775000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_commit_transaction+0x2d88/0x37e0 fs/btrfs/transaction.c:2550
flush_space+0x9a3/0xe60 fs/btrfs/space-info.c:811
btrfs_async_reclaim_metadata_space+0x29b/0x340 fs/btrfs/space-info.c:1084
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup