[syzbot] [bcachefs?] WARNING: ODEBUG bug in delete_node (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 22a40d14b572 Linux 6.10-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10624699980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1ace69f521989b1f
dashboard link: https://syzkaller.appspot.com/bug?extid=8771878f9b32e4731b79
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/d8763ab76416/disk-22a40d14.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f4fc1fb5933b/vmlinux-22a40d14.xz
kernel image: https://storage.googleapis.com/syzbot-assets/66b91c8c2a1c/bzImage-22a40d14.xz

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

------------[ cut here ]------------
ODEBUG: activate active (active state 0) object: ffff888061b5aed8 object type: rcu_head hint: 0x0
WARNING: CPU: 1 PID: 5226 at lib/debugobjects.c:517 debug_print_object+0x17a/0x1f0 lib/debugobjects.c:514
Modules linked in:
CPU: 1 PID: 5226 Comm: syz.3.12 Not tainted 6.10.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:debug_print_object+0x17a/0x1f0 lib/debugobjects.c:514
Code: e8 cb a9 4a fd 4c 8b 0b 48 c7 c7 80 20 1f 8c 48 8b 74 24 08 48 89 ea 44 89 e1 4d 89 f8 ff 34 24 e8 0b 6c aa fc 48 83 c4 08 90 <0f> 0b 90 90 ff 05 3c 6d fe 0a 48 83 c4 10 5b 41 5c 41 5d 41 5e 41
RSP: 0018:ffffc900047e78b8 EFLAGS: 00010286
RAX: df2335102b84e500 RBX: ffffffff8bcbd3e0 RCX: 0000000000040000
RDX: ffffc90009f1c000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffffff8c1f2200 R08: ffffffff81585742 R09: fffffbfff1c39994
R10: dffffc0000000000 R11: fffffbfff1c39994 R12: 0000000000000000
R13: ffffffff8c1f2118 R14: dffffc0000000000 R15: ffff888061b5aed8
FS: 00007f202ffff6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f62c5f6d000 CR3: 000000007e0ea000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
debug_object_activate+0x357/0x510 lib/debugobjects.c:732
debug_rcu_head_queue kernel/rcu/rcu.h:227 [inline]
__call_rcu_common kernel/rcu/tree.c:3057 [inline]
call_rcu+0x97/0xa70 kernel/rcu/tree.c:3176
radix_tree_node_free lib/radix-tree.c:310 [inline]
delete_node+0x1ac/0x770 lib/radix-tree.c:573
radix_tree_delete_item+0x2e0/0x3f0 lib/radix-tree.c:1430
__bch2_fs_stop+0x230/0x540 fs/bcachefs/super.c:626
generic_shutdown_super+0x136/0x2d0 fs/super.c:642
bch2_kill_sb+0x41/0x50 fs/bcachefs/fs.c:2044
deactivate_locked_super+0xc4/0x130 fs/super.c:473
cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1267
task_work_run+0x24f/0x310 kernel/task_work.c:180
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [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+0x168/0x360 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f203057729a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 7e 1a 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f202fffee78 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffec RBX: 00007f202fffef00 RCX: 00007f203057729a
RDX: 000000002000fec0 RSI: 000000002000ff00 RDI: 00007f202fffeec0
RBP: 000000002000fec0 R08: 00007f202fffef00 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 000000002000ff00
R13: 00007f202fffeec0 R14: 000000000000fe88 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