syzbot


INFO: task hung in rfkill_global_led_trigger_worker

Status: upstream: reported C repro on 2025/06/17 07:16
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+400f23dd04603030f0ee@syzkaller.appspotmail.com
First crash: 169d, last: 11d
Bug presence (1)
Date Name Commit Repro Result
2025/11/13 upstream (ToT) 6fa9041b7177 C [report] INFO: task hung in rfkill_global_led_trigger_worker
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 1468d 1504d 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 151 5d13h 987d 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 7604 6m 501d 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 511d 1113d 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 214d 1000d 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 1340d 1452d 0/1 auto-closed as invalid on 2022/07/31 23:38

Sample crash report:
INFO: task kworker/0:0:8 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:0     state:D stack:25688 pid:8     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/0:1:9 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:1     state:D stack:25072 pid:9     ppid:2      flags:0x00004000
Workqueue: events rfkill_op_handler
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:995 [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_epo+0x79/0x180 net/rfkill/core.c:466
 __rfkill_handle_global_op net/rfkill/input.c:60 [inline]
 rfkill_op_handler+0x84/0x240 net/rfkill/input.c:108
 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.0.17:5964 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.17        state:D stack:25128 pid:5964  ppid:5915   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_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_unregister+0xc8/0x220 net/rfkill/core.c:1149
 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+0xf6/0x180 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:0x7f9696d8f6c9
RSP: 002b:00007fff1e0c5998 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 0000000000022354 RCX: 00007f9696d8f6c9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000001 R09: 000000061e0c5c8f
R10: 0000001b2da20000 R11: 0000000000000246 R12: 00007f9696fe5fac
R13: 00007f9696fe5fa0 R14: ffffffffffffffff R15: 0000000000000002
 </TASK>

Showing all locks held in the system:
3 locks held by kworker/0:0/8:
 #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: ffffc900000d7d00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc900000d7d00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8e297928 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x27/0xd0 net/rfkill/core.c:182
4 locks held by kworker/0:1/9:
 #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: ffffc900000e7d00 ((rfkill_op_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc900000e7d00 ((rfkill_op_work).work){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffffffff8e297928 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_epo+0x47/0x180 net/rfkill/core.c:462
 #3: ffff88802ba14100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:995 [inline]
 #3: ffff88802ba14100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
 #3: ffff88802ba14100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x2e0 net/nfc/core.c:179
1 lock held by khungtaskd/28:
 #0: ffffffff8cd2fee0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8cd2fee0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8cd2fee0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by getty/5548:
 #0: ffff8880313e00a0 (&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
2 locks held by syz.0.17/5964:
 #0: ffff88802ba14100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:995 [inline]
 #0: ffff88802ba14100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x63/0x2a0 net/nfc/core.c:1165
 #1: ffffffff8e297928 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xc8/0x220 net/rfkill/core.c:1149
2 locks held by syz-executor/6049:
 #0: ffff88802c5b7118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x650 drivers/bluetooth/hci_vhci.c:479
 #1: ffffffff8e297928 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x37/0x8e0 net/rfkill/core.c:1075
2 locks held by syz-executor/6056:
 #0: ffff88806d154918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x650 drivers/bluetooth/hci_vhci.c:479
 #1: ffffffff8e297928 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x37/0x8e0 net/rfkill/core.c:1075
2 locks held by syz-executor/6063:
 #0: ffff888078b65118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x650 drivers/bluetooth/hci_vhci.c:479
 #1: ffffffff8e297928 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x37/0x8e0 net/rfkill/core.c:1075

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 49 Comm: kworker/u4:3 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:preempt_count_add+0x14a/0x1a0 kernel/sched/core.c:5848
Code: 80 c1 03 38 c1 0f 8c 00 ff ff ff 89 fb 48 c7 c7 80 f4 ea 96 e8 57 7c 81 00 89 df e9 eb fe ff ff 48 c7 c1 80 f4 ea 96 80 e1 07 <80> c1 03 38 c1 0f 8c 05 ff ff ff 89 fb 48 c7 c7 80 f4 ea 96 e8 2d
RSP: 0018:ffffc90000ba7860 EFLAGS: 00000046
RAX: 0000000000000004 RBX: 0000000000000000 RCX: ffffffff96eaf400
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffffc90000ba7ab0 R08: ffffffff8e4a8d6f R09: 1ffffffff1c951ad
R10: dffffc0000000000 R11: fffffbfff1c951ae R12: 0000000000000000
R13: ffff8880b8f3c200 R14: ffff8880b8f3c200 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000558afedbd190 CR3: 000000000cb30000 CR4: 00000000003506e0
Call Trace:
 <TASK>
 raw_spin_rq_lock_nested+0x1e/0x140 kernel/sched/core.c:556
 raw_spin_rq_lock kernel/sched/sched.h:1372 [inline]
 rq_lock kernel/sched/sched.h:1681 [inline]
 __schedule+0x2dd/0x44d0 kernel/sched/core.c:6613
 schedule+0xbd/0x170 kernel/sched/core.c:6773
 toggle_allocation_gate+0x162/0x250 mm/kfence/core.c:833
 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>

Crashes (14):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/11/12 01:46 linux-6.6.y 0a805b6ea8cd 4e1406b4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in rfkill_global_led_trigger_worker
2025/11/21 17:23 linux-6.6.y 0a805b6ea8cd 280ea308 .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/11/13 09:44 linux-6.6.y 0a805b6ea8cd 07e030de .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/11/12 19:53 linux-6.6.y 0a805b6ea8cd 07e030de .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/10/20 05:37 linux-6.6.y f231f248323d 1c8c8cd8 .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/10/04 04:11 linux-6.6.y f34f16e5c632 49379ee0 .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/09/21 12:56 linux-6.6.y af1544b5d072 67c37560 .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/09/05 00:24 linux-6.6.y 355bd0b51d2f d291dd2d .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/29 14:39 linux-6.6.y cc1a1c5b404a 3e1beec6 .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/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.