syzbot


INFO: task hung in reg_check_chans_work

Status: upstream: reported on 2025/06/17 22:04
Reported-by: syzbot+2e8a009d0669eed02147@syzkaller.appspotmail.com
First crash: 119d, last: 13d
Similar bugs (14)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in reg_check_chans_work 1 10 342d 627d 0/3 auto-obsoleted due to no activity on 2025/02/14 20:30
linux-6.1 INFO: task hung in reg_check_chans_work (2) 1 1 298d 298d 0/3 auto-obsoleted due to no activity on 2025/03/30 18:04
upstream INFO: task hung in reg_check_chans_work (6) wireless 1 C error 129 465d 539d 26/29 fixed on 2024/07/09 19:14
upstream INFO: task hung in reg_check_chans_work (3) wireless 1 60 1410d 1474d 0/29 auto-closed as invalid on 2022/04/03 20:03
linux-4.14 INFO: task hung in reg_check_chans_work 1 1 1256d 1256d 0/1 auto-obsoleted due to no activity on 2022/09/05 08:58
upstream INFO: task hung in reg_check_chans_work (7) wireless 1 C error 755 1d22h 387d 0/29 upstream: reported C repro on 2024/09/23 08:39
upstream INFO: task hung in reg_check_chans_work (4) wireless 1 4 1203d 1205d 0/29 auto-closed as invalid on 2022/09/28 14:08
upstream INFO: task hung in reg_check_chans_work net 1 15 2740d 2800d 0/29 closed as dup on 2018/02/14 15:33
linux-6.1 INFO: task hung in reg_check_chans_work (3) 1 1 192d 192d 0/3 auto-obsoleted due to no activity on 2025/07/15 07:58
android-44 INFO: task hung in reg_check_chans_work 1 18 2712d 2786d 0/2 auto-closed as invalid on 2019/02/22 14:50
android-49 INFO: task hung in reg_check_chans_work 1 18 2712d 2810d 0/3 auto-closed as invalid on 2019/02/22 15:19
linux-6.1 INFO: task hung in reg_check_chans_work 1 3 489d 507d 0/3 auto-obsoleted due to no activity on 2024/09/20 17:51
upstream INFO: task hung in reg_check_chans_work (5) wireless 1 26 717d 845d 0/29 auto-obsoleted due to no activity on 2024/01/08 12:17
upstream INFO: task hung in reg_check_chans_work (2) wireless 1 3 1835d 1843d 0/29 auto-closed as invalid on 2021/01/04 12:48

Sample crash report:
INFO: task kworker/0:4:5840 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:4     state:D stack:21360 pid:5840  ppid:2      flags:0x00004000
Workqueue: events_power_efficient reg_check_chans_work
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
 wiphy_lock include/net/cfg80211.h:5777 [inline]
 reg_leave_invalid_chans net/wireless/reg.c:2451 [inline]
 reg_check_chans_work+0x104/0xd70 net/wireless/reg.c:2466
 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:
4 locks held by kworker/u4:0/11:
3 locks held by kworker/u4:1/12:
2 locks held by kworker/1:0/23:
 #0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #1: ffffc900001d7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc900001d7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
1 lock held by khungtaskd/29:
 #0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
1 lock held by kcompactd0/32:
4 locks held by kworker/u4:3/48:
5 locks held by kworker/u4:5/990:
2 locks held by kworker/u4:7/2882:
3 locks held by kworker/R-ipv6_/3149:
 #0: ffff88814c7e9138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #0: ffff88814c7e9138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #1: ffffc9000c547d20 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc9000c547d20 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8dfbb208 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x19/0x30 net/ipv6/addrconf.c:4700
1 lock held by klogd/5144:
3 locks held by udevd/5155:
3 locks held by dhcpcd/5449:
4 locks held by dhcpcd/5450:
2 locks held by getty/5547:
 #0: ffff88814ca610a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000326e2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
1 lock held by syz-executor/5773:
2 locks held by syz-executor/5785:
2 locks held by udevd/5799:
4 locks held by kworker/0:6/5872:
3 locks held by kworker/1:5/5873:
 #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: ffffc90004b1fd00 (free_ipc_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc90004b1fd00 (free_ipc_work){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8cd357f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
 #2: ffffffff8cd357f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x448/0x830 kernel/rcu/tree_exp.h:1004
2 locks held by syz-executor/8815:
1 lock held by syz.2.1935/11229:
3 locks held by syz-executor/11291:
4 locks held by kworker/0:5/11292:

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x39b/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xf41/0xf80 kernel/hung_task.c:379
 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>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/02 01:04 linux-6.6.y 147338df3487 267f56c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in reg_check_chans_work
2025/08/21 14:29 linux-6.6.y bb9c90ab9c5a 3e79b825 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in reg_check_chans_work
2025/08/20 09:40 linux-6.6.y bb9c90ab9c5a 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in reg_check_chans_work
2025/07/09 15:13 linux-6.6.y a5df3a702b2c f4e5e155 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in reg_check_chans_work
2025/06/17 22:03 linux-6.6.y c2603c511feb e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf INFO: task hung in reg_check_chans_work
* Struck through repros no longer work on HEAD.