[v5.15] WARNING in kfree_rcu_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b911329317b4 Linux 5.15.133
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ded54e680000
kernel config: https://syzkaller.appspot.com/x/.config?x=c21a1ede2e21ef2f
dashboard link: https://syzkaller.appspot.com/bug?extid=8a34a2a8b94a9401347e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0d67112bfdd3/disk-b9113293.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/54ed715e08ee/vmlinux-b9113293.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cec49685c149/Image-b9113293.gz.xz

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

------------[ cut here ]------------
ODEBUG: active_state not available (active state 0) object type: rcu_head hint: 0x0
WARNING: CPU: 0 PID: 4064 at lib/debugobjects.c:511 debug_print_object lib/debugobjects.c:508 [inline]
WARNING: CPU: 0 PID: 4064 at lib/debugobjects.c:511 debug_object_active_state+0x278/0x3e8 lib/debugobjects.c:965
Modules linked in:
CPU: 0 PID: 4064 Comm: kworker/0:8 Not tainted 5.15.133-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
Workqueue: events kfree_rcu_work
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : debug_print_object lib/debugobjects.c:508 [inline]
pc : debug_object_active_state+0x278/0x3e8 lib/debugobjects.c:965
lr : debug_print_object lib/debugobjects.c:508 [inline]
lr : debug_object_active_state+0x278/0x3e8 lib/debugobjects.c:965
sp : ffff80001d1c7a00
x29: ffff80001d1c7a00 x28: 0000000000000000 x27: dfff800000000000
x26: ffff800011acabc0 x25: ffff0000c5ed8e00 x24: 0000000000000001
x23: 0000000000000000 x22: 0000000000000000 x21: ffff800018700000
x20: ffff800011acabc0 x19: 0000000000000000 x18: 1fffe000368fef8e
x17: 1fffe000368fef8e x16: ffff8000082ea5e4 x15: ffff80001499efe0
x14: 1ffff0000292006a x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000832c8d0 x10: 0000000000000000 x9 : f82a59abb203c700
x8 : f82a59abb203c700 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff800008045860
x2 : 0000000000000006 x1 : 0000000100000000 x0 : 0000000000000053
Call trace:
debug_print_object lib/debugobjects.c:508 [inline]
debug_object_active_state+0x278/0x3e8 lib/debugobjects.c:965
debug_rcu_head_unqueue kernel/rcu/rcu.h:185 [inline]
debug_rcu_bhead_unqueue kernel/rcu/tree.c:3175 [inline]
kfree_rcu_work+0x250/0x6c0 kernel/rcu/tree.c:3274
process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
irq event stamp: 13180
hardirqs last enabled at (13179): [<ffff800008268afc>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1338 [inline]
hardirqs last enabled at (13179): [<ffff800008268afc>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:4780
hardirqs last disabled at (13180): [<ffff80001195f638>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (13078): [<ffff800008370f54>] local_bh_enable+0xc/0x2c include/linux/bottom_half.h:31
softirqs last disabled at (13074): [<ffff800008370f28>] local_bh_disable+0xc/0x2c include/linux/bottom_half.h:18
---[ end trace a498e9a747efde31 ]---


---
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 overwrite 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.