syzbot


INFO: task hung in linkwatch_event

Status: upstream: reported on 2025/07/04 13:16
Reported-by: syzbot+a255043cadd915b831d0@syzkaller.appspotmail.com
First crash: 62d, last: 4d15h
Similar bugs (18)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in linkwatch_event (2) 1 1 208d 208d 0/3 auto-obsoleted due to no activity on 2025/05/19 15:08
linux-6.1 INFO: task hung in linkwatch_event (4) 1 syz 7 84d 175d 0/3 upstream: reported syz repro on 2025/03/13 04:56
android-414 INFO: task hung in linkwatch_event 1 C 7 2119d 2339d 0/1 public: reported C repro on 2019/04/10 16:14
linux-4.14 INFO: task hung in linkwatch_event (2) 1 1 1140d 1140d 0/1 auto-obsoleted due to no activity on 2022/11/19 11:58
android-44 INFO: task hung in linkwatch_event 1 6 2555d 2700d 0/2 auto-closed as invalid on 2019/03/05 13:11
linux-5.15 INFO: task hung in linkwatch_event 1 84 306d 602d 0/3 auto-obsoleted due to no activity on 2025/01/11 00:55
upstream INFO: task hung in linkwatch_event (4) net 1 C done 3309 2h16m 404d 0/29 upstream: reported C repro on 2024/07/27 06:21
upstream INFO: task hung in linkwatch_event net 1 C 82 2147d 2759d 0/29 closed as dup on 2018/02/14 15:33
linux-4.14 INFO: task hung in linkwatch_event 1 5 1823d 1950d 0/1 auto-closed as invalid on 2021/01/05 01:42
linux-4.19 INFO: task hung in linkwatch_event (2) 1 C error 217 914d 2003d 0/1 upstream: reported C repro on 2020/03/11 20:12
upstream INFO: task hung in linkwatch_event (2) net 1 C done done 1033 1228d 1954d 20/29 fixed on 2022/05/13 11:13
linux-4.19 INFO: task hung in linkwatch_event 1 3 2156d 2270d 0/1 auto-closed as invalid on 2020/02/07 01:11
upstream INFO: task hung in linkwatch_event (3) net 1 1634 422d 1017d 26/29 fixed on 2024/07/09 19:14
linux-4.14 INFO: task hung in linkwatch_event (3) 1 2 974d 975d 0/1 upstream: reported on 2023/01/03 10:49
android-49 INFO: task hung in linkwatch_event 1 13 2319d 2335d 0/3 auto-closed as invalid on 2019/10/25 08:50
linux-6.1 INFO: task hung in linkwatch_event (2) 1 32 358d 472d 0/3 auto-obsoleted due to no activity on 2024/11/21 00:32
linux-6.1 INFO: task hung in linkwatch_event 1 2 760d 876d 0/3 auto-obsoleted due to no activity on 2023/11/14 00:59
linux-6.1 INFO: task hung in linkwatch_event (3) 1 1 283d 283d 0/3 auto-obsoleted due to no activity on 2025/03/05 15:51

Sample crash report:
INFO: task kworker/u4:24:9839 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:24   state:D stack:23624 pid:9839  ppid:2      flags:0x00004000
Workqueue: events_unbound linkwatch_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5380 [inline]
 __schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
 schedule+0xbd/0x170 kernel/sched/core.c:6773
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6832
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b7/0xcc0 kernel/locking/mutex.c:747
 linkwatch_event+0xe/0x60 net/core/link_watch.c:286
 process_one_work kernel/workqueue.c:2634 [inline]
 process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
 worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/28:
 #0: ffffffff8cd2fbe0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8cd2fbe0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8cd2fbe0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
3 locks held by kworker/0:3/5175:
 #0: ffff888017870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #0: ffff888017870938 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #1: ffffc90003387d00 (deferred_process_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc90003387d00 (deferred_process_work){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8dfbc348 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xe/0x20 net/switchdev/switchdev.c:104
2 locks held by dhcpcd/5454:
2 locks held by getty/5556:
 #0: ffff8880315320a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
2 locks held by dhcpcd/5591:
3 locks held by kworker/1:4/5885:
 #0: ffff888017871d38 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #0: ffff888017871d38 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #1: ffffc90004a9fd00 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc90004a9fd00 ((reg_check_chans).work){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8dfbc348 (rtnl_mutex){+.+.}-{3:3}, at: reg_check_chans_work+0x91/0xd70 net/wireless/reg.c:2463
3 locks held by kworker/u4:19/9821:
3 locks held by kworker/u4:20/9826:
 #0: ffff88802c104538 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #0: ffff88802c104538 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #1: ffffc9000d02fd00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc9000d02fd00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8dfbc348 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x19/0x30 net/ipv6/addrconf.c:4700
3 locks held by kworker/u4:24/9839:
 #0: ffff888017871538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #0: ffff888017871538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #1: ffffc9001021fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc9001021fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8dfbc348 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xe/0x60 net/core/link_watch.c:286
1 lock held by dhcpcd/16989:
1 lock held by syz.2.4577/18473:
 #0: ffffffff8dfbc348 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
 #0: ffffffff8dfbc348 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x41/0x1c0 drivers/net/tun.c:3511
1 lock held by syz.2.4577/18474:
 #0: ffffffff8dfbc348 (rtnl_mutex){+.+.}-{3:3}, at: dev_ioctl+0x7d2/0x1170 net/core/dev_ioctl.c:785
1 lock held by syz.2.4577/18491:
2 locks held by syz.6.4578/18475:

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/31 09:29 linux-6.6.y cc1a1c5b404a 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf INFO: task hung in linkwatch_event
2025/08/22 16:32 linux-6.6.y bb9c90ab9c5a bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in linkwatch_event
2025/07/04 13:16 linux-6.6.y 3f5b4c104b7d 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in linkwatch_event
* Struck through repros no longer work on HEAD.