[v6.6] INFO: task hung in nsim_drv_remove

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cbb31f77b879 Linux 6.6.121
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16bbf13a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2a950bf7c0bff9f9
dashboard link: https://syzkaller.appspot.com/bug?extid=729ec771091615685175
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170cd244580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12919eb2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/487f8544b25c/disk-cbb31f77.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/129a28b457e8/vmlinux-cbb31f77.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47e034f9408f/bzImage-cbb31f77.xz

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

INFO: task syz-executor:5906 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:22248 pid:5906 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6833
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x6a9/0xcc0 kernel/locking/mutex.c:747
nsim_drv_remove+0x50/0x160 drivers/net/netdevsim/dev.c:1675
device_remove drivers/base/dd.c:567 [inline]
__device_release_driver drivers/base/dd.c:1272 [inline]
device_release_driver_internal+0x468/0x7a0 drivers/base/dd.c:1295
bus_remove_device+0x342/0x400 drivers/base/bus.c:576
device_del+0x522/0x910 drivers/base/core.c:3872


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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