[v6.1] INFO: task hung in new_device_store (4)
0 views
Skip to first unread message
syzbot
Aug 17, 2026, 11:27:27 PM (3 hours ago) Aug 17
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: e4f7d8be268e Linux 6.1.182
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117eb949580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=1ad49174883efdf4fc89
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156843a60452/disk-e4f7d8be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/719d532a0151/vmlinux-e4f7d8be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/12160bc2f9ec/bzImage-e4f7d8be.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1ad491...@syzkaller.appspotmail.com
INFO: task syz-executor:19899 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:22928 pid:19899 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5246 [inline]
__schedule+0x107f/0x4030 kernel/sched/core.c:6563
schedule+0xb9/0x180 kernel/sched/core.c:6639
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
new_device_store+0x139/0x690 drivers/net/netdevsim/bus.c:160
kernfs_fop_write_iter+0x3a0/0x520 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+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f996e35e90e
RSP: 002b:00007fff0a9b2e48 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000555571e6f500 RCX: 00007f996e35e90e
RDX: 0000000000000003 RSI: 00007fff0a9b2ed0 RDI: 0000000000000005
RBP: 00007f996e4358cb R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000003
R13: 00007fff0a9b2ed0 R14: 00007f996f154620 R15: 0000000000000003
</TASK>
INFO: task syz-executor:19939 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:22928 pid:19939 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5246 [inline]
__schedule+0x107f/0x4030 kernel/sched/core.c:6563
schedule+0xb9/0x180 kernel/sched/core.c:6639
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
kernfs_fop_write_iter+0x3a0/0x520 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+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd5f0d5e90e
RSP: 002b:00007ffdc575bf98 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00005555713a3500 RCX: 00007fd5f0d5e90e
RDX: 0000000000000001 RSI: 00007ffdc575c020 RDI: 0000000000000005
RBP: 00007fd5f0e358a7 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffdc575c020 R14: 00007fd5f1b54620 R15: 0000000000000003
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2e4f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2ed10 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6527
1 lock held by dhcpcd/3933:
2 locks held by getty/4029:
#0: ffff88814d80e098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41e/0x1360 drivers/tty/n_tty.c:2198
2 locks held by kworker/0:13/4536:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90004cbfd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
6 locks held by kworker/u4:17/4595:
#0: ffff88801761e938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90004e4fd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd4ead0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffff8880453d12f8 (&devlink->lock_key#19){+.+.}-{3:3}, at: devlink_pernet_pre_exit+0x104/0x280 net/devlink/leftover.c:12502
#4: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: nsim_destroy+0x3b/0x150 drivers/net/netdevsim/netdev.c:381
#5: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#5: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
3 locks held by kworker/u4:27/4618:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc9000509fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
7 locks held by syz-executor/19894:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff8880794d6488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
#4: ffff88806097f0e8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#4: ffff88806097f0e8 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1099 [inline]
#4: ffff88806097f0e8 (&dev->mutex){....}-{3:3}, at: device_release_driver_internal+0xb1/0x7c0 drivers/base/dd.c:1302
#5: ffff88806097a2f8 (&devlink->lock_key#16){+.+.}-{3:3}, at: nsim_drv_remove+0x54/0x170 drivers/net/netdevsim/dev.c:1678
#6: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#6: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
4 locks held by syz-executor/19899:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff8880729fb088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c830 (kn->active#54){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c830 (kn->active#54){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x139/0x690 drivers/net/netdevsim/bus.c:160
4 locks held by syz-executor/19939:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff8880272a3088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19950:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff88802825c888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19962:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888074cd3888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19970:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888066ccf488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19980:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888055737488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19996:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888085eae488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20002:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888033c4e888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20007:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888061dea488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20012:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff88807e46fc88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20017:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888061de9c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20052:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff88802af28488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20063:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888063ba6488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20071:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff88804532ec88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20081:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff8880558c6888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
---
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 found the following issue on:
HEAD commit: e4f7d8be268e Linux 6.1.182
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117eb949580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=1ad49174883efdf4fc89
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156843a60452/disk-e4f7d8be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/719d532a0151/vmlinux-e4f7d8be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/12160bc2f9ec/bzImage-e4f7d8be.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1ad491...@syzkaller.appspotmail.com
INFO: task syz-executor:19899 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:22928 pid:19899 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5246 [inline]
__schedule+0x107f/0x4030 kernel/sched/core.c:6563
schedule+0xb9/0x180 kernel/sched/core.c:6639
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
new_device_store+0x139/0x690 drivers/net/netdevsim/bus.c:160
kernfs_fop_write_iter+0x3a0/0x520 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+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f996e35e90e
RSP: 002b:00007fff0a9b2e48 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000555571e6f500 RCX: 00007f996e35e90e
RDX: 0000000000000003 RSI: 00007fff0a9b2ed0 RDI: 0000000000000005
RBP: 00007f996e4358cb R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000003
R13: 00007fff0a9b2ed0 R14: 00007f996f154620 R15: 0000000000000003
</TASK>
INFO: task syz-executor:19939 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:22928 pid:19939 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5246 [inline]
__schedule+0x107f/0x4030 kernel/sched/core.c:6563
schedule+0xb9/0x180 kernel/sched/core.c:6639
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
kernfs_fop_write_iter+0x3a0/0x520 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+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd5f0d5e90e
RSP: 002b:00007ffdc575bf98 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00005555713a3500 RCX: 00007fd5f0d5e90e
RDX: 0000000000000001 RSI: 00007ffdc575c020 RDI: 0000000000000005
RBP: 00007fd5f0e358a7 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffdc575c020 R14: 00007fd5f1b54620 R15: 0000000000000003
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2e4f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2ed10 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6527
1 lock held by dhcpcd/3933:
2 locks held by getty/4029:
#0: ffff88814d80e098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41e/0x1360 drivers/tty/n_tty.c:2198
2 locks held by kworker/0:13/4536:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90004cbfd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
6 locks held by kworker/u4:17/4595:
#0: ffff88801761e938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90004e4fd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd4ead0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffff8880453d12f8 (&devlink->lock_key#19){+.+.}-{3:3}, at: devlink_pernet_pre_exit+0x104/0x280 net/devlink/leftover.c:12502
#4: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: nsim_destroy+0x3b/0x150 drivers/net/netdevsim/netdev.c:381
#5: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#5: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
3 locks held by kworker/u4:27/4618:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc9000509fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
7 locks held by syz-executor/19894:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff8880794d6488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
#4: ffff88806097f0e8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:885 [inline]
#4: ffff88806097f0e8 (&dev->mutex){....}-{3:3}, at: __device_driver_lock drivers/base/dd.c:1099 [inline]
#4: ffff88806097f0e8 (&dev->mutex){....}-{3:3}, at: device_release_driver_internal+0xb1/0x7c0 drivers/base/dd.c:1302
#5: ffff88806097a2f8 (&devlink->lock_key#16){+.+.}-{3:3}, at: nsim_drv_remove+0x54/0x170 drivers/net/netdevsim/dev.c:1678
#6: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#6: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
4 locks held by syz-executor/19899:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff8880729fb088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c830 (kn->active#54){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c830 (kn->active#54){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x139/0x690 drivers/net/netdevsim/bus.c:160
4 locks held by syz-executor/19939:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff8880272a3088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19950:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff88802825c888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19962:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888074cd3888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19970:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888066ccf488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19980:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888055737488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/19996:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888085eae488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20002:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888033c4e888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20007:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888061dea488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20012:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff88807e46fc88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20017:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888061de9c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20052:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff88802af28488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20063:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff888063ba6488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20071:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff88804532ec88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
#2: ffff888026c2c918 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x520 fs/kernfs/file.c:344
#3: ffffffff8d66a3a8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xd3/0x370 drivers/net/netdevsim/bus.c:209
4 locks held by syz-executor/20081:
#0: ffff88807f7ae460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#1: ffff8880558c6888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1d8/0x520 fs/kernfs/file.c:343
---
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
Reply all
Reply to author
Forward
0 new messages