[syzbot] [kernel?] BUG: workqueue leaked atomic, lock or RCU: kworker/NUM:NUM[NUM]

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 09cf85ef183a Merge branch 'ipv4-namespacify-ipv4-address-h..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14bc2b27980000
kernel config: https://syzkaller.appspot.com/x/.config?x=97682d9a9859be7a
dashboard link: https://syzkaller.appspot.com/bug?extid=21814e89fd126bbfb79c
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/f07fbcff269f/disk-09cf85ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/27b386159ee2/vmlinux-09cf85ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0d9909f42c33/bzImage-09cf85ef.xz

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

BUG: workqueue leaked atomic, lock or RCU: kworker/0:4[5280]
preempt=0x00000000 lock=0->0 RCU=0->0 workfn=nsim_dev_trap_report_work
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 5280 Comm: kworker/0:4 Not tainted 6.12.0-rc1-syzkaller-00360-g09cf85ef183a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events nsim_dev_trap_report_work

Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
process_one_work kernel/workqueue.c:3250 [inline]
process_scheduled_works+0x1158/0x1850 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</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.