[v5.15] INFO: task hung in new_device_store

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 115472395b0a Linux 5.15.104
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15c1cf29c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5592cc4916e1c2f
dashboard link: https://syzkaller.appspot.com/bug?extid=9afcd388831dfdaf4f29
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=130f2815c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6c2c0744c7e0/disk-11547239.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ea4c5ecca4f/vmlinux-11547239.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a231dbcf423/bzImage-11547239.xz

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

INFO: task syz-executor.2:3737 blocked for more than 143 seconds.
Not tainted 5.15.104-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D
stack:21656 pid: 3737 ppid: 1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6511
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
new_device_store+0x1b0/0x910 drivers/net/netdevsim/bus.c:295
kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f3baae24e7f
RSP: 002b:00007ffde92b3050 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f3baae24e7f
RDX: 0000000000000003 RSI: 00007ffde92b30a0 RDI: 0000000000000005
RBP: 0000000000000005 R08: 0000000000000000 R09: 00007ffde92b2ff0
R10: 0000000000000000 R11: 0000000000000293 R12: 00007f3baaece772
R13: 00007ffde92b30a0 R14: 0000000000000000 R15: 00007ffde92b3770
</TASK>
INFO: task syz-executor.3:3744 blocked for more than 144 seconds.
Not tainted 5.15.104-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:21656 pid: 3744 ppid: 1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6511
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
new_device_store+0x1b0/0x910 drivers/net/netdevsim/bus.c:295
kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fba1d9e9e7f
RSP: 002b:00007ffe144a8210 EFLAGS: 00000293
ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fba1d9e9e7f
RDX: 0000000000000003 RSI: 00007ffe144a8260 RDI: 0000000000000005
RBP: 0000000000000005 R08: 0000000000000000 R09: 00007ffe144a81b0
R10: 0000000000000000 R11: 0000000000000293 R12: 00007fba1da93772
R13: 00007ffe144a8260 R14: 0000000000000000 R15: 00007ffe144a8930
</TASK>
INFO: task syz-executor.4:3746 blocked for more than 144 seconds.
Not tainted 5.15.104-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:21336 pid: 3746 ppid: 1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6511
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
new_device_store+0x1b0/0x910 drivers/net/netdevsim/bus.c:295
kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8ad45a7e7f
RSP: 002b:00007fffec231890 EFLAGS: 00000293
ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f8ad45a7e7f
RDX: 0000000000000003 RSI: 00007fffec2318e0 RDI: 0000000000000005
RBP: 0000000000000005 R08: 0000000000000000 R09: 00007fffec231830
R10: 0000000000000000 R11: 0000000000000293 R12: 00007f8ad4651772
R13: 00007fffec2318e0 R14: 0000000000000000 R15: 00007fffec231fb0
</TASK>

Showing all locks held in the system:
3 locks held by kworker/1:1/25:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90000dffd20 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
#2: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
1 lock held by khungtaskd/27:
#0:
ffffffff8c91b920 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
1 lock held by khugepaged/33:
#0: ffffffff8c9b19a8 (lock#4){+.+.}-{3:3}, at: __lru_add_drain_all+0x67/0x9e0 mm/swap.c:782
4 locks held by kworker/u4:3/155:
#0: ffff888011db5138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90001cbfd20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
#2: ffffffff8d9c7a90 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:558
#3: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: netdev_run_todo+0xa4f/0xc40 net/core/dev.c:10627
3 locks held by kworker/0:4/2922:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc9000c017d20 (reg_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
#2: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: reg_todo+0x18/0x1990 net/wireless/reg.c:3166
1 lock held by dhcpcd/3171:
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: __netlink_dump_start+0x12e/0x6f0 net/netlink/af_netlink.c:2376
2 locks held by getty/3278:
#0: ffff888023e5b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900020a32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
6 locks held by kworker/0:8/3672:
4 locks held by syz-executor.2/3737:
#0: ffff88807f74e460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x29a/0xe50 fs/read_write.c:590
#1: ffff88806e677488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e7/0x4f0 fs/kernfs/file.c:287
#2: ffff888147fcc918
(kn->active#205){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x20b/0x4f0 fs/kernfs/file.c:288
#3: ffffffff8d351f28 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x1b0/0x910 drivers/net/netdevsim/bus.c:295
6 locks held by syz-executor.1/3742:
#0:
ffff88807f74e460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x29a/0xe50 fs/read_write.c:590
#1: ffff88806a894888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e7/0x4f0 fs/kernfs/file.c:287
#2: ffff888147fcc918 (kn->active#205){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x20b/0x4f0 fs/kernfs/file.c:288
#3: ffffffff8d351f28 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x1b0/0x910 drivers/net/netdevsim/bus.c:295
#4: ffff888078372178 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#4: ffff888078372178 (&dev->mutex){....}-{3:3}, at: __device_attach+0x8a/0x570 drivers/base/dd.c:949
#5: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: devlink_nl_port_fill+0x2ab/0x930 net/core/devlink.c:995
4 locks held by syz-executor.3/3744:
#0: ffff88807f74e460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x29a/0xe50 fs/read_write.c:590
#1: ffff88806ad40888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e7/0x4f0 fs/kernfs/file.c:287
#2: ffff888147fcc918 (kn->active#205){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x20b/0x4f0 fs/kernfs/file.c:288
#3: ffffffff8d351f28 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x1b0/0x910 drivers/net/netdevsim/bus.c:295
4 locks held by syz-executor.4/3746:
#0: ffff88807f74e460 (sb_writers
#8
){.+.+}-{0:0}, at: vfs_write+0x29a/0xe50 fs/read_write.c:590
#1: ffff888019f1dc88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e7/0x4f0 fs/kernfs/file.c:287
#2: ffff888147fcc918 (kn->active#205){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x20b/0x4f0 fs/kernfs/file.c:288
#3:
ffffffff8d351f28 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x1b0/0x910 drivers/net/netdevsim/bus.c:295
1 lock held by syz-executor.5/3749:
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3431
1 lock held by syz-executor.2/4048:
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3431
1 lock held by syz-executor.1/4054:
#0:
ffffffff8d9d37e8
(rtnl_mutex
){+.+.}-{3:3}
, at: netdev_run_todo+0xa4f/0xc40 net/core/dev.c:10627
2 locks held by syz-executor.3/4056:
#0:
ffffffff8d9d37e8
(rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
(rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5584
#1:
ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:840
1 lock held by syz-executor.4/4059:
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3431
1 lock held by syz-executor.5/4062:
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3431
1 lock held by syz-executor.2/4111:
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5584
1 lock held by syz-executor.1/4118:
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5584
1 lock held by syz-executor.3/4119:
#0:
ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5584
1 lock held by syz-executor.4/4123:
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5584
1 lock held by syz-executor.5/4126:
#0:
ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
ffffffff8d9d37e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5584
1 lock held by dhcpcd/4133:
#0: ffff8880714bca10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff8880714bca10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
#0: ffff8880714bca10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x98/0x230 net/socket.c:1317
1 lock held by dhcpcd/4134:
#0: ffff88806788c120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff88806788c120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
1 lock held by dhcpcd/4135:
#0: ffff88801a5b6120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff88801a5b6120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
2 locks held by dhcpcd/4136:
#0: ffff88801a300120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff88801a300120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:840

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.104-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3672 Comm: kworker/0:8 Not tainted 5.15.104-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events uhid_device_add_worker
RIP: 0010:io_serial_in+0x72/0xb0 drivers/tty/serial/8250/8250_port.c:460
Code: 24 45 0a fd 89 e9 41 d3 e6 48 83 c3 40 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 d5 8c 53 fd 44 03 33 44 89 f2 ec <0f> b6 c0 5b 41 5e 41 5f 5d c3 89 e9 80 e1 07 38 c1 7c ad 48 89 ef
RSP: 0018:ffffc9000340ed70 EFLAGS: 00000002
RAX: 1ffffffff22dae60 RBX: ffffffff916d7180 RCX: 0000000000000000
RDX: 00000000000003fd RSI: 0000000000000000 RDI: 0000000000000020
RBP: 0000000000000000 R08: ffffffff847572b2 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: 0000000000000037
R13: ffffffff916d7140 R14: 00000000000003fd R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000558a55c8e1b0 CR3: 0000000022e60000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
serial_in drivers/tty/serial/8250/8250.h:117 [inline]
wait_for_xmitr+0x51/0x260 drivers/tty/serial/8250/8250_port.c:2076
serial8250_console_putchar+0x19/0x50 drivers/tty/serial/8250/8250_port.c:3312
uart_console_write+0xa9/0x100 drivers/tty/serial/serial_core.c:1971
serial8250_console_write+0xc8e/0x1180 drivers/tty/serial/8250/8250_port.c:3389
console_unlock+0xced/0x12b0 kernel/printk/printk.c:2734
vprintk_emit+0xba/0x150 kernel/printk/printk.c:2268
dev_vprintk_emit+0x2aa/0x323 drivers/base/core.c:4595
dev_printk_emit+0xd9/0x118 drivers/base/core.c:4606
_dev_warn+0x11e/0x165 drivers/base/core.c:4662
hid_parser_main+0x749/0xae0 drivers/hid/hid-core.c:634
hid_open_report+0xacd/0x1450 drivers/hid/hid-core.c:1267
hid_parse include/linux/hid.h:1062 [inline]
hid_generic_probe+0x39/0x80 drivers/hid/hid-generic.c:63
hid_device_probe+0x2a6/0x3a0 drivers/hid/hid-core.c:2301
really_probe+0x24e/0xb60 drivers/base/dd.c:595
__driver_probe_device+0x1c3/0x3f0 drivers/base/dd.c:750
driver_probe_device+0x50/0x420 drivers/base/dd.c:780
__device_attach_driver+0x2b9/0x500 drivers/base/dd.c:902
bus_for_each_drv+0x183/0x200 drivers/base/bus.c:427
__device_attach+0x359/0x570 drivers/base/dd.c:974
bus_probe_device+0xba/0x1e0 drivers/base/bus.c:487
device_add+0xb48/0xfd0 drivers/base/core.c:3394
hid_add_device+0x37f/0x4c0 drivers/hid/hid-core.c:2451
uhid_device_add_worker+0x40/0xe0 drivers/hid/uhid.c:73
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.