syzbot


INFO: task hung in rfkill_global_led_trigger_worker

Status: upstream: reported on 2025/06/17 07:16
Reported-by: syzbot+400f23dd04603030f0ee@syzkaller.appspotmail.com
First crash: 71d, last: 3d22h
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in rfkill_global_led_trigger_worker wireless 1 3 1371d 1407d 0/29 auto-closed as invalid on 2022/01/24 07:42
linux-6.1 INFO: task hung in rfkill_global_led_trigger_worker origin:upstream 1 C 143 3d13h 890d 0/3 upstream: reported C repro on 2023/03/21 21:11
upstream INFO: task hung in rfkill_global_led_trigger_worker (3) wireless 1 C 2291 10m 404d 0/29 closed as dup on 2025/06/17 10:11
upstream INFO: task hung in rfkill_global_led_trigger_worker (2) net nfc 1 C error 1362 414d 1016d 26/29 fixed on 2024/07/09 19:14
linux-5.15 INFO: task hung in rfkill_global_led_trigger_worker origin:upstream 1 C error 63 117d 903d 0/3 upstream: reported C repro on 2023/03/08 16:06
linux-4.19 INFO: task hung in rfkill_global_led_trigger_worker 1 7 1243d 1354d 0/1 auto-closed as invalid on 2022/07/31 23:38

Sample crash report:
INFO: task kworker/1:6:12076 blocked for more than 143 seconds.
      Not tainted 6.6.102-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:6     state:D stack:27120 pid:12076 ppid:2      flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
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
 rfkill_global_led_trigger_worker+0x27/0xd0 net/rfkill/core.c:182
 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>
INFO: task kworker/1:7:12077 blocked for more than 143 seconds.
      Not tainted 6.6.102-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:7     state:D stack:25640 pid:12077 ppid:2      flags:0x00004000
Workqueue: events rfkill_sync_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
 device_lock include/linux/device.h:992 [inline]
 nfc_dev_down net/nfc/core.c:143 [inline]
 nfc_rfkill_set_block+0x50/0x2e0 net/nfc/core.c:179
 rfkill_set_block+0x1c6/0x420 net/rfkill/core.c:346
 rfkill_sync net/rfkill/core.c:379 [inline]
 rfkill_sync_work+0x114/0x200 net/rfkill/core.c:1060
 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>
INFO: task syz.3.3452:15241 blocked for more than 143 seconds.
      Not tainted 6.6.102-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.3452      state:D stack:27016 pid:15241 ppid:11288  flags:0x00004004
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_timeout+0x9b/0x280 kernel/time/timer.c:2143
 do_wait_for_common kernel/sched/completion.c:95 [inline]
 __wait_for_common kernel/sched/completion.c:116 [inline]
 wait_for_common kernel/sched/completion.c:127 [inline]
 wait_for_completion+0x2bd/0x590 kernel/sched/completion.c:148
 __flush_work+0x895/0x9f0 kernel/workqueue.c:3430
 __cancel_work_timer+0x3b0/0x520 kernel/workqueue.c:3517
 rfkill_unregister+0x92/0x220 net/rfkill/core.c:1143
 nfc_unregister_device+0x96/0x2a0 net/nfc/core.c:1167
 virtual_ncidev_close+0x59/0x90 drivers/nfc/virtual_ncidev.c:172
 __fput+0x234/0x970 fs/file_table.c:384
 task_work_run+0x1ce/0x250 kernel/task_work.c:239
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
 __syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
 syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
 do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb32c98ebe9
RSP: 002b:00007ffcbc28a448 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00000000000a6502 RCX: 00007fb32c98ebe9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007fb32cbb7da0 R08: 0000000000000001 R09: 00000007bc28a73f
R10: 0000001b2cf20000 R11: 0000000000000246 R12: 00007fb32cbb5fac
R13: 00007fb32cbb5fa0 R14: ffffffffffffffff R15: 00007ffcbc28a560
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #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
2 locks held by getty/5550:
 #0: ffff88814cba10a0 (&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
3 locks held by kworker/1:6/12076:
 #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: ffffc9000feafd00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc9000feafd00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8e297268 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x27/0xd0 net/rfkill/core.c:182
4 locks held by kworker/1:7/12077:
 #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: ffffc9000fecfd00 ((work_completion)(&rfkill->sync_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc9000fecfd00 ((work_completion)(&rfkill->sync_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8e297268 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_sync_work+0x2e/0x200 net/rfkill/core.c:1059
 #3: ffff88807dfd5100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:992 [inline]
 #3: ffff88807dfd5100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
 #3: ffff88807dfd5100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x2e0 net/nfc/core.c:179
1 lock held by syz.3.3452/15241:
 #0: ffff88807dfd5100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:992 [inline]
 #0: ffff88807dfd5100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x63/0x2a0 net/nfc/core.c:1165
2 locks held by syz-executor/15345:
 #0: ffff888079690118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x6e0 drivers/bluetooth/hci_vhci.c:471
 #1: ffffffff8e297268 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x37/0x8e0 net/rfkill/core.c:1075
2 locks held by syz.2.3506/15383:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
 #1: ffffffff8e297268 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_open+0x12d/0x820 net/rfkill/core.c:1182
1 lock held by syz.2.3506/15385:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz.2.3506/15387:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz.1.3511/15397:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz.0.3513/15406:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz-executor/15409:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz-executor/15412:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz-executor/15413:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz-executor/15415:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz-executor/15417:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz-executor/15420:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz-executor/15421:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143
1 lock held by syz-executor/15423:
 #0: ffffffff8d4c37a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5a/0x370 drivers/char/misc.c:143

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted 6.6.102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/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
CPU: 0 PID: 169 Comm: kworker/u4:5 Not tainted 6.6.102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue:  0x0 (events_unbound)
RIP: 0010:detach_task+0x137/0x340 kernel/sched/fair.c:9039
Code: 00 0f 1f 44 00 00 41 80 3c 17 00 4c 8b 34 24 74 08 48 89 ef e8 0a 96 7b 00 48 8b 7b 08 4c 89 f6 ba 08 00 00 00 e8 89 67 fa ff <48> 83 c3 14 48 89 d8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df 0f
RSP: 0018:ffffc90002e77540 EFLAGS: 00000082
RAX: ffff8880b8f3c51c RBX: ffffc90002e77960 RCX: dffffc0000000000
RDX: ffff8880186a5ab8 RSI: 0000000000000001 RDI: ffff8880b8f3c51c
RBP: ffffc90002e77968 R08: ffffffff8e4a882f R09: 1ffffffff1c95105
R10: dffffc0000000000 R11: fffffbfff1c95106 R12: ffff8880186a5f6c
R13: 1ffff110030d4bed R14: ffff8880186a5a00 R15: 1ffff920005cef2d
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe17696fabf CR3: 000000000cb30000 CR4: 00000000003506f0
Call Trace:
 <TASK>
 detach_tasks kernel/sched/fair.c:9174 [inline]
 load_balance+0x3e40/0x54a0 kernel/sched/fair.c:11367
 newidle_balance+0x696/0x1050 kernel/sched/fair.c:12381
 balance_fair+0x38/0x70 kernel/sched/fair.c:8284
 put_prev_task_balance kernel/sched/core.c:5979 [inline]
 pick_next_task kernel/sched/core.c:6119 [inline]
 __schedule+0x26df/0x44d0 kernel/sched/core.c:6661
 schedule+0xbd/0x170 kernel/sched/core.c:6773
 worker_thread+0xc01/0xfc0 kernel/workqueue.c:2807
 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>

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/24 05:23 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 rfkill_global_led_trigger_worker
2025/08/07 07:09 linux-6.6.y 3a8ababb8b6a 9a42d6b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in rfkill_global_led_trigger_worker
2025/08/04 20:40 linux-6.6.y 3a8ababb8b6a f5bcc8dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in rfkill_global_led_trigger_worker
2025/08/02 02:29 linux-6.6.y 3a8ababb8b6a 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in rfkill_global_led_trigger_worker
2025/06/17 07:16 linux-6.6.y c2603c511feb cfebc887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in rfkill_global_led_trigger_worker
* Struck through repros no longer work on HEAD.