[v5.15] WARNING in call_rcu (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 26c690eff0a5 Linux 5.15.146
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13f901a9e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=dc70d39e176dd118
dashboard link: https://syzkaller.appspot.com/bug?extid=d24c850070b319a318dc
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/40141853e0d3/disk-26c690ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/87e1356f3f98/vmlinux-26c690ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/77c63c93083b/bzImage-26c690ef.xz

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

------------[ cut here ]------------
ODEBUG: active_state not available (active state 0) object type: rcu_head hint: 0x0
WARNING: CPU: 1 PID: 3540 at lib/debugobjects.c:511 debug_print_object lib/debugobjects.c:508 [inline]
WARNING: CPU: 1 PID: 3540 at lib/debugobjects.c:511 debug_object_active_state+0x287/0x410 lib/debugobjects.c:965
Modules linked in:
CPU: 1 PID: 3540 Comm: syz-executor.0 Not tainted 5.15.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:debug_print_object lib/debugobjects.c:508 [inline]
RIP: 0010:debug_object_active_state+0x287/0x410 lib/debugobjects.c:965
Code: 89 ef e8 9c c6 bd fd 4c 8b 45 00 48 c7 c7 c0 86 d8 8a 48 c7 c6 20 84 d8 8a 48 c7 c2 60 88 d8 8a 31 c9 49 89 d9 e8 39 c9 3f fd <0f> 0b e9 9f 00 00 00 45 31 f6 ff 05 19 1d 61 0d 43 0f b6 04 2f 84
RSP: 0018:ffffc90002d87d00 EFLAGS: 00010246
RAX: 20848aa4a1e65700 RBX: 0000000000000000 RCX: ffff88801c271dc0
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffffff8a8c13e0 R08: ffffffff81665dbc R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: dffffc0000000000 R14: 0000000000000001 R15: ffff88807d828000
FS: 00005555558f0480(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f623f1ec440 CR3: 000000007c58d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
debug_rcu_head_queue kernel/rcu/rcu.h:177 [inline]
__call_rcu kernel/rcu/tree.c:2991 [inline]
call_rcu+0xb1/0xa70 kernel/rcu/tree.c:3087
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f4169865c1a
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 03 7f 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 63 7f 02 00 8b 44 24
RSP: 002b:00007fffa1c2ff30 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f4169865c1a
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 0000000000000005 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000050012
R13: 00007fffa1c2ff70 R14: 00007f416a4be690 R15: 00007f416a4be620
</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

[syzbot]

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