[v5.15] WARNING in call_rcu

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1378525aa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c67dae6b27f0d6cd
dashboard link: https://syzkaller.appspot.com/bug?extid=534336e578b5a01a41f4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4aa2cbf1e81c/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2ebee78b098c/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4e17f9ac4b6a/bzImage-d54cfc42.xz

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

------------[ cut here ]------------
ODEBUG: active_state not available (active state 0) object type: rcu_head hint: 0x0
WARNING: CPU: 1 PID: 3659 at lib/debugobjects.c:511 debug_print_object lib/debugobjects.c:508 [inline]
WARNING: CPU: 1 PID: 3659 at lib/debugobjects.c:511 debug_object_active_state+0x287/0x410 lib/debugobjects.c:965
Modules linked in:
CPU: 1 PID: 3659 Comm: syz-executor.0 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/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 ac 4f be fd 4c 8b 45 00 48 c7 c7 40 6b d8 8a 48 c7 c6 a0 68 d8 8a 48 c7 c2 e0 6c d8 8a 31 c9 49 89 d9 e8 c9 ad 40 fd <0f> 0b e9 9f 00 00 00 45 31 f6 ff 05 f9 53 62 0d 43 0f b6 04 2f 84
RSP: 0018:ffffc900041afd00 EFLAGS: 00010246
RAX: 1ed9263bf17f1900 RBX: 0000000000000000 RCX: ffff888079db0000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffffff8a8c01c0 R08: ffffffff8166491c R09: ffffed1017364f24
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: dffffc0000000000 R14: 0000000000000001 R15: ffff88801f132f00
FS: 0000555556f13400(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc794cfd000 CR3: 000000007245a000 CR4: 00000000003506e0
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:2978 [inline]
call_rcu+0xb1/0xa70 kernel/rcu/tree.c:3074
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:0x7f287c03d12b
Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44
RSP: 002b:00007ffe8951fba0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007f287c03d12b
RDX: 0000000000000004 RSI: 00007ffe8951fbe0 RDI: 0000000000000003
RBP: 0000000000000003 R08: 0000000000000000 R09: 00007ffe8951fb30
R10: 0000000000000000 R11: 0000000000000293 R12: 00007f287c0d651b
R13: 00007ffe8951fbe0 R14: 0000000000000001 R15: 00007ffe89520180
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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.