[v6.1] WARNING in btrfs_put_transaction

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1210a2f9c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ccbc3d5467efd1
dashboard link: https://syzkaller.appspot.com/bug?extid=9260df5ea39aadc883a0
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7fe538fc87bf/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8df93997601a/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/03ad7e3bf859/Image-543aff19.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 11218 at fs/btrfs/transaction.c:132 btrfs_put_transaction+0x308/0x378 fs/btrfs/transaction.c:131
Modules linked in:
CPU: 1 PID: 11218 Comm: btrfs-transacti Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : btrfs_put_transaction+0x308/0x378 fs/btrfs/transaction.c:131
lr : btrfs_put_transaction+0x308/0x378 fs/btrfs/transaction.c:131
sp : ffff80002d1d7b00
x29: ffff80002d1d7b00 x28: ffff000128ec2028 x27: ffff000128ec2000
x26: 1fffe0001b28199d x25: ffff80002d1d7ce0 x24: dfff800000000000
x23: ffff0000d940cce8 x22: dfff800000000000 x21: 0000000000000001
x20: ffff000128ec2330 x19: ffff000128ec2000 x18: ffff80002d1d7520
x17: ffff80000a0db168 x16: ffff80000825d1ac x15: 000000000003f856
x14: 1ffff00002ab00b0 x13: dfff800000000000 x12: 0000000000000001
x11: ff8080000a0e6654 x10: 0000000000000000 x9 : ffff80000a0e6654
x8 : ffff0000c7f39b40 x7 : ffff80000a0db170 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000a0e63bc
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000001
Call trace:
btrfs_put_transaction+0x308/0x378 fs/btrfs/transaction.c:131
btrfs_cleanup_transaction+0x498/0x1574 fs/btrfs/disk-io.c:5246
transaction_kthread+0x33c/0x44c fs/btrfs/disk-io.c:1920
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
irq event stamp: 250
hardirqs last enabled at (249): [<ffff8000121b9b0c>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (249): [<ffff8000121b9b0c>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (250): [<ffff8000120d75ac>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (0): [<ffff8000081a2a44>] copy_process+0x13c0/0x38d0 kernel/fork.c:2201
softirqs last disabled at (0): [<0000000000000000>] 0x0
---[ end trace 0000000000000000 ]---


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

[syzbot]

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