syzbot


INFO: task hung in new_device_store

Status: auto-closed as invalid on 2022/07/18 12:08
Subsystems: net
[Documentation on labels]
First crash: 735d, last: 735d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in new_device_store (3) net 12 243d 430d 0/26 auto-obsoleted due to no activity on 2023/11/22 09:08
linux-5.15 INFO: task hung in new_device_store syz error 1 394d 394d 0/3 auto-obsoleted due to no activity on 2023/07/24 22:37
upstream INFO: task hung in new_device_store (2) net 1 567d 567d 0/26 auto-obsoleted due to no activity on 2023/01/15 11:32
linux-5.15 INFO: task hung in new_device_store (2) 1 92d 92d 0/3 upstream: reported on 2024/01/22 03:38

Sample crash report:
INFO: task syz-executor.0:2039 blocked for more than 430 seconds.
      Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0  state:D stack:    0 pid: 2039 ppid:  2035 flags:0x00000000
Call Trace:
[<ffffffff831a68fe>] schedule+0x74/0x14c kernel/sched/core.c:6369
[<ffffffff831a709c>] schedule_preempt_disabled+0x16/0x28 kernel/sched/core.c:6428
[<ffffffff831a92b2>] __mutex_lock_common kernel/locking/mutex.c:673 [inline]
[<ffffffff831a92b2>] __mutex_lock+0x522/0xade kernel/locking/mutex.c:733
[<ffffffff831a9882>] mutex_lock_nested+0x14/0x1c kernel/locking/mutex.c:785
[<ffffffff819ca160>] new_device_store+0x106/0x46a drivers/net/netdevsim/bus.c:174
[<ffffffff813e9a5e>] bus_attr_store+0x4e/0x6e drivers/base/bus.c:122
[<ffffffff8066f0dc>] sysfs_kf_write+0x9c/0xbe fs/sysfs/file.c:136
[<ffffffff8066de8a>] kernfs_fop_write_iter+0x264/0x32e fs/kernfs/file.c:296
[<ffffffff804c4ce0>] call_write_iter include/linux/fs.h:2074 [inline]
[<ffffffff804c4ce0>] new_sync_write+0x296/0x3aa fs/read_write.c:503
[<ffffffff804c86f4>] vfs_write+0x2de/0x334 fs/read_write.c:590
[<ffffffff804c8aae>] ksys_write+0x10a/0x224 fs/read_write.c:643
[<ffffffff804c8bf0>] __do_sys_write fs/read_write.c:655 [inline]
[<ffffffff804c8bf0>] sys_write+0x28/0x36 fs/read_write.c:652
[<ffffffff80005716>] ret_from_syscall+0x0/0x2

Showing all locks held in the system:
2 locks held by kworker/1:0/20:
1 lock held by khungtaskd/27:
 #0: ffffffff84b73e00 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x3c/0x20e kernel/locking/lockdep.c:6462
2 locks held by kworker/u4:6/1206:
 #0: ffffaf8007229138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:630 [inline]
 #0: ffffaf8007229138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:658 [inline]
 #0: ffffaf8007229138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x524/0xffe kernel/workqueue.c:2278
 #1: ffffaf800ee9bcf0 ((kfence_timer).work){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:630 [inline]
 #1: ffffaf800ee9bcf0 ((kfence_timer).work){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:658 [inline]
 #1: ffffaf800ee9bcf0 ((kfence_timer).work){+.+.}-{0:0}, at: process_one_work+0x524/0xffe kernel/workqueue.c:2278
2 locks held by getty/1981:
 #0: ffffaf805a4d8098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3a/0x46 drivers/tty/tty_ldsem.c:340
 #1: ffff8f8010b082e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xa52/0xbac drivers/tty/n_tty.c:2077
2 locks held by syz-fuzzer/2019:
3 locks held by kworker/1:1/2029:
 #0: ffffaf800f0e7938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:630 [inline]
 #0: ffffaf800f0e7938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:658 [inline]
 #0: ffffaf800f0e7938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x524/0xffe kernel/workqueue.c:2278
 #1: ffffaf800bf6bcf0 ((addr_chk_work).work){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:630 [inline]
 #1: ffffaf800bf6bcf0 ((addr_chk_work).work){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:658 [inline]
 #1: ffffaf800bf6bcf0 ((addr_chk_work).work){+.+.}-{0:0}, at: process_one_work+0x524/0xffe kernel/workqueue.c:2278
 #2: ffffffff855cf108 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x22/0x2a net/core/rtnetlink.c:72
6 locks held by syz-executor.1/2038:
4 locks held by syz-executor.0/2039:
 #0: ffffaf800c044460 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x104/0x334 fs/read_write.c:586
 #1: ffffaf800ee16088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1fc/0x32e fs/kernfs/file.c:287
 #2: ffffaf800eba8660 (kn->active#124){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x20e/0x32e fs/kernfs/file.c:288
 #3: ffffffff8515a428 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x106/0x46a drivers/net/netdevsim/bus.c:174

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


Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/04/19 12:02 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d c334415e .config console log report info ci-qemu2-riscv64 INFO: task hung in new_device_store
* Struck through repros no longer work on HEAD.