[moderation] [bcachefs?] WARNING: still has locks held in __bch2_trans_get

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9221b2819b8a Add linux-next specific files for 20240503
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=103ceec0980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8ab537f51a6a0d98
dashboard link: https://syzkaller.appspot.com/bug?extid=7ecd1fb462c28e0dfd83
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bfo...@redhat.com kent.ov...@linux.dev linux-b...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3e67dbdc3c37/disk-9221b281.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ade618fa19f8/vmlinux-9221b281.xz
kernel image: https://storage.googleapis.com/syzbot-assets/df12e5073c97/bzImage-9221b281.xz

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

====================================
WARNING: syz-executor.0/7273 still has locks held!
6.9.0-rc6-next-20240503-syzkaller #0 Not tainted
------------------------------------
1 lock held by syz-executor.0/7273:
#0: ffff88807f604258 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:116 [inline]
#0: ffff88807f604258 (&c->btree_trans_barrier){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:215 [inline]
#0: ffff88807f604258 (&c->btree_trans_barrier){.+.+}-{0:0}, at: __bch2_trans_get+0x9b7/0xe00 fs/bcachefs/btree_iter.c:3202

stack backtrace:
CPU: 0 PID: 7273 Comm: syz-executor.0 Not tainted 6.9.0-rc6-next-20240503-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
do_exit+0x1b5f/0x27e0 kernel/exit.c:904
do_group_exit+0x207/0x2c0 kernel/exit.c:1023
get_signal+0x16a1/0x1740 kernel/signal.c:2909
arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xc9/0x370 kernel/entry/common.c:218
do_syscall_64+0x102/0x240 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f118667dca9
Code: Unable to access opcode bytes at 0x7f118667dc7f.
RSP: 002b:00007f11873db0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: 0000000000001000 RBX: 00007f11867abf80 RCX: 00007f118667dca9
RDX: 0000000000002020 RSI: 0000000020000600 RDI: 0000000000000005
RBP: 00007f11873db120 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 000000000000000b R14: 00007f11867abf80 R15: 00007ffca6bf13d8
</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