[syzbot] [bcachefs?] WARNING in bch2_trans_put

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ba16c1cf11c9 Merge tag 'edac_urgent_for_v6.9' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13791cf4980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9d7ea7de0cb32587
dashboard link: https://syzkaller.appspot.com/bug?extid=291aef749c5cbb9ca2fd
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: https://storage.googleapis.com/syzbot-assets/bf33b57f5750/disk-ba16c1cf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5656c2dd228d/vmlinux-ba16c1cf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8807d572a9fd/bzImage-ba16c1cf.xz

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

------------[ cut here ]------------
btree trans held srcu lock (delaying memory reclaim) for 14 seconds
WARNING: CPU: 0 PID: 29792 at fs/bcachefs/btree_iter.c:2873 check_srcu_held_too_long fs/bcachefs/btree_iter.c:2871 [inline]
WARNING: CPU: 0 PID: 29792 at fs/bcachefs/btree_iter.c:2873 bch2_trans_put+0xd8c/0xf90 fs/bcachefs/btree_iter.c:3113
Modules linked in:
CPU: 0 PID: 29792 Comm: syz-executor.3 Not tainted 6.9.0-rc7-syzkaller-00188-gba16c1cf11c9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:check_srcu_held_too_long fs/bcachefs/btree_iter.c:2871 [inline]
RIP: 0010:bch2_trans_put+0xd8c/0xf90 fs/bcachefs/btree_iter.c:3113
Code: 2b 1e 48 c1 eb 02 48 b9 c3 f5 28 5c 8f c2 f5 28 48 89 d8 48 f7 e1 48 c1 ea 02 48 c7 c7 40 28 11 8c 48 89 d6 e8 c5 71 49 fd 90 <0f> 0b 90 90 e9 2d f8 ff ff e8 86 ff 86 fd 90 0f 0b 90 e9 70 f8 ff
RSP: 0018:ffffc9000504ef78 EFLAGS: 00010246
RAX: 25f7e0a65c980f00 RBX: 000000000000015e RCX: 0000000000040000
RDX: ffffc9000b21b000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: dffffc0000000000 R08: ffffffff81587c52 R09: fffffbfff1c39b5c
R10: dffffc0000000000 R11: fffffbfff1c39b5c R12: 1ffff11003daf808
R13: 1ffff11003daf80d R14: ffff88801ed7c068 R15: ffff88801ed7c041
FS: 00007f0b753806c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd53b17db38 CR3: 000000007c3e4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
bch2_btree_root_read+0x8b2/0x970 fs/bcachefs/btree_io.c:1772
read_btree_roots+0x22d/0x7b0 fs/bcachefs/recovery.c:457
bch2_fs_recovery+0x4334/0x63b0 fs/bcachefs/recovery.c:785
bch2_fs_start+0x356/0x5b0 fs/bcachefs/super.c:1043
bch2_fs_open+0xa8d/0xdf0 fs/bcachefs/super.c:2105
bch2_mount+0x71d/0x1320 fs/bcachefs/fs.c:1903
legacy_get_tree+0xee/0x190 fs/fs_context.c:662
vfs_get_tree+0x90/0x2a0 fs/super.c:1779
do_new_mount+0x2be/0xb40 fs/namespace.c:3352
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0b7467f46a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0b7537fef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f0b7537ff80 RCX: 00007f0b7467f46a
RDX: 0000000020011a00 RSI: 0000000020011a40 RDI: 00007f0b7537ff40
RBP: 0000000020011a00 R08: 00007f0b7537ff80 R09: 0000000001200014
R10: 0000000001200014 R11: 0000000000000202 R12: 0000000020011a40
R13: 00007f0b7537ff40 R14: 00000000000119fc R15: 0000000020000100
</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 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