[v6.1] INFO: task hung in new_device_store (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 779f9571ac3e Linux 6.1.164
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17392006580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b1adc0bfde2d8a4a
dashboard link: https://syzkaller.appspot.com/bug?extid=b303c42fad7d04f72047
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/85e761437fc4/disk-779f9571.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0f3aa7ae77ae/vmlinux-779f9571.xz
kernel image: https://storage.googleapis.com/syzbot-assets/baba59a67bd9/Image-779f9571.gz.xz

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

INFO: task syz-executor:8591 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:0 pid:8591 ppid:1 flags:0x00000001
Call trace:
__switch_to+0x2f4/0x550 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xdd0/0x1b0c kernel/sched/core.c:6562
schedule+0xc4/0x170 kernel/sched/core.c:6638
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6697
__mutex_lock_common+0xafc/0x1f60 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
new_device_store+0x138/0x514 drivers/net/netdevsim/bus.c:160
bus_attr_store+0x80/0xa4 drivers/base/bus.c:124
sysfs_kf_write+0x1f8/0x278 fs/sysfs/file.c:136
kernfs_fop_write_iter+0x348/0x4c0 fs/kernfs/file.c:352
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x3ec/0x7f0 fs/read_write.c:584
ksys_write+0x12c/0x224 fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Showing all locks held in the system:
2 locks held by init/1:
3 locks held by kworker/u4:1/11:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x6b8/0x13a4 kernel/workqueue.c:2265
#1: ffff80001c9d7c20 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x6fc/0x13a4 kernel/workqueue.c:2267
#2: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
1 lock held by rcu_tasks_kthre/12:
#0: ffff8000153e7c30 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x40/0xbb4 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffff8000153e8450 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x40/0xbb4 kernel/rcu/tasks.h:517
1 lock held by ksoftirqd/1/21:
3 locks held by kworker/1:1/24:
#0: ffff0000d6628538 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x6b8/0x13a4 kernel/workqueue.c:2265
#1: ffff80001cab7c20 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x6fc/0x13a4 kernel/workqueue.c:2267
#2: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
1 lock held by khungtaskd/28:
#0: ffff8000153e72c0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by kworker/u4:2/39:
1 lock held by klogd/3924:
1 lock held by dhcpcd/3990:
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x650/0xcdc net/core/rtnetlink.c:6147
2 locks held by getty/4078:
#0: ffff0000d0fc3098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80002090b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x2ec/0xfa0 drivers/tty/n_tty.c:2198
2 locks held by kworker/0:3/4366:
#0: ffff0000c0021938 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x6b8/0x13a4 kernel/workqueue.c:2265
#1: ffff8000210d7c20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x6fc/0x13a4 kernel/workqueue.c:2267
2 locks held by kworker/0:4/4367:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x6b8/0x13a4 kernel/workqueue.c:2265
#1: ffff8000210e7c20 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x6fc/0x13a4 kernel/workqueue.c:2267
5 locks held by kworker/u4:8/4556:
#0: ffff0000c0845138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x6b8/0x13a4 kernel/workqueue.c:2265
#1: ffff8000212a7c20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x6fc/0x13a4 kernel/workqueue.c:2267
#2: ffff8000178728d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x134/0xa84 net/core/net_namespace.c:594
#3: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
#4: ffff00012911cd00 (team->team_lock_key#8){+.+.}-{3:3}, at: team_del_slave+0x30/0x180 drivers/net/team/team.c:2016
3 locks held by kworker/0:15/4660:
#0: ffff0000d6628538 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x6b8/0x13a4 kernel/workqueue.c:2265
#1: ffff8000216b7c20 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x6fc/0x13a4 kernel/workqueue.c:2267
#2: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
3 locks held by kworker/1:14/5254:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x6b8/0x13a4 kernel/workqueue.c:2265
#1: ffff800021977c20 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x6fc/0x13a4 kernel/workqueue.c:2267
#2: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
1 lock held by syz-executor/7615:
1 lock held by syz-executor/7616:
#0: ffff8000153ecf78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#0: ffff8000153ecf78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2b8/0x77c kernel/rcu/tree_exp.h:962
3 locks held by syz-executor/7642:
#0: ffff0000d9d0d0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff0000d9d0d0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1f0/0x4a4 net/bluetooth/hci_core.c:2705
#1: ffff0000d9d0c078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x398/0xec8 net/bluetooth/hci_sync.c:5233
#2: ffff8000179d3f68 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffff8000179d3f68 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xb0/0x26c net/bluetooth/hci_conn.c:2504
4 locks held by syz-executor/8591:
#0: ffff0000d8e88460 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x244/0x7f0 fs/read_write.c:580
#1: ffff00010ff3c088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1c0/0x4c0 fs/kernfs/file.c:343
#2: ffff0000d074a830 (kn->active#51){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff0000d074a830 (kn->active#51){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x200/0x4c0 fs/kernfs/file.c:344
#3: ffff800016c29188 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x138/0x514 drivers/net/netdevsim/bus.c:160
4 locks held by syz-executor/8594:
#0: ffff0000d8e88460 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x244/0x7f0 fs/read_write.c:580
#1: ffff0001175f9c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1c0/0x4c0 fs/kernfs/file.c:343
#2: ffff0000d074a830 (kn->active#51){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff0000d074a830 (kn->active#51){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x200/0x4c0 fs/kernfs/file.c:344
#3: ffff800016c29188 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x138/0x514 drivers/net/netdevsim/bus.c:160
7 locks held by syz-executor/8766:
#0: ffff0000d8e88460 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x244/0x7f0 fs/read_write.c:580
#1: ffff0000f9bc8c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1c0/0x4c0 fs/kernfs/file.c:343
#2: ffff0000d074a918 (kn->active#50){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff0000d074a918 (kn->active#50){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x200/0x4c0 fs/kernfs/file.c:344
#3: ffff800016c29188 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xdc/0x32c drivers/net/netdevsim/bus.c:209
#4: ffff00010b63b0e8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:840 [inline]
#4: ffff00010b63b0e8 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1080 [inline]
#4: ffff00010b63b0e8 (&dev->mutex){....}-{3:3}, at: device_release_driver_internal+0x9c/0x6d0 drivers/base/dd.c:1283
#5: ffff00010b63e2f8 (&devlink->lock_key#19){+.+.}-{3:3}, at: devl_lock+0x24/0x34 net/devlink/leftover.c:275
#6: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
1 lock held by syz-executor/9093:
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x650/0xcdc net/core/rtnetlink.c:6147
1 lock held by syz-executor/9098:
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x650/0xcdc net/core/rtnetlink.c:6147
1 lock held by syz-executor/9103:
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x650/0xcdc net/core/rtnetlink.c:6147
1 lock held by syz-executor/9109:
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x650/0xcdc net/core/rtnetlink.c:6147
1 lock held by syz-executor/9113:
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x650/0xcdc net/core/rtnetlink.c:6147
1 lock held by syz-executor/9118:
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffff80001787f188 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x650/0xcdc net/core/rtnetlink.c:6147

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



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