[syzbot] [kernel?] INFO: task hung in rescuer_thread (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9a9424c756fe net: usb: sr9700: remove code to drive nonexi..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17040a52580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2c36acc86fd56a9d
dashboard link: https://syzkaller.appspot.com/bug?extid=1d6360305e34d30ab396
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=115d0a5a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/aca10cd84bc5/disk-9a9424c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/65bf8ad42e4f/vmlinux-9a9424c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a69a5e1088ef/bzImage-9a9424c7.xz

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

INFO: task kworker/R-wg-cr:5992 blocked for more than 149 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/R-wg-cr state:D stack:25984 pid:5992 tgid:5992 ppid:2 task_flags:0x4208060 flags:0x00080000
Workqueue: 0x0 (wg-crypt-wg1)
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5260 [inline]
__schedule+0x14ea/0x5050 kernel/sched/core.c:6867
__schedule_loop kernel/sched/core.c:6949 [inline]
schedule+0x164/0x360 kernel/sched/core.c:6964
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7021
__mutex_lock_common kernel/locking/mutex.c:692 [inline]
__mutex_lock+0x7fe/0x1300 kernel/locking/mutex.c:776
worker_detach_from_pool kernel/workqueue.c:2730 [inline]
rescuer_thread+0x593/0x1390 kernel/workqueue.c:3560
kthread+0x726/0x8b0 kernel/kthread.c:463
ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
</TASK>

Showing all locks held in the system:
1 lock held by kworker/R-rcu_g/4:
#0: ffffffff8e3f8c88 (wq_pool_attach_mutex){+.+.}-{4:4}, at: worker_detach_from_pool kernel/workqueue.c:2730 [inline]
#0: ffffffff8e3f8c88 (wq_pool_attach_mutex){+.+.}-{4:4}, at: rescuer_thread+0x593/0x1390 kernel/workqueue.c:3560


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