syzbot


INFO: task hung in rfkill_global_led_trigger_worker

Status: upstream: reported C repro on 2023/03/21 21:11
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+1479ca5713663c4e70bc@syzkaller.appspotmail.com
First crash: 395d, last: 1d06h
Bug presence (2)
Date Name Commit Repro Result
2023/12/25 upstream (ToT) 861deac3b092 C [report] INFO: task hung in misc_open
2024/04/08 upstream (ToT) fec50db7033e C Failed due to an error; will retry later
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in rfkill_global_led_trigger_worker wireless 3 876d 912d 0/26 auto-closed as invalid on 2022/01/24 07:42
upstream INFO: task hung in rfkill_global_led_trigger_worker (2) net nfc C error 1027 14h42m 521d 0/26 upstream: reported C repro on 2022/11/15 16:56
linux-5.15 INFO: task hung in rfkill_global_led_trigger_worker origin:upstream C error 62 179d 408d 0/3 upstream: reported C repro on 2023/03/08 16:06
linux-4.19 INFO: task hung in rfkill_global_led_trigger_worker 7 748d 859d 0/1 auto-closed as invalid on 2022/07/31 23:38
Fix bisection attempts (3)
Created Duration User Patch Repo Result
2024/03/23 16:21 2h44m bisect fix linux-6.1.y job log (0) log
2023/12/25 10:42 1h33m bisect fix linux-6.1.y job log (0) log
2023/11/24 09:41 1h47m bisect fix linux-6.1.y job log (0) log

Sample crash report:
INFO: task kworker/0:4:3570 blocked for more than 143 seconds.
      Not tainted 6.1.45-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:4     state:D stack:27640 pid:3570  ppid:2      flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x132c/0x4330 kernel/sched/core.c:6554
 schedule+0xbf/0x180 kernel/sched/core.c:6630
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
 __mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
 process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292
 worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439
 kthread+0x26e/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
INFO: task syz-executor136:3580 blocked for more than 143 seconds.
      Not tainted 6.1.45-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor136 state:D stack:24056 pid:3580  ppid:3539   flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x132c/0x4330 kernel/sched/core.c:6554
 schedule+0xbf/0x180 kernel/sched/core.c:6630
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
 __mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 rfkill_unregister+0xcc/0x220 net/rfkill/core.c:1130
 nfc_unregister_device+0x92/0x290 net/nfc/core.c:1167
 virtual_ncidev_close+0x55/0x90 drivers/nfc/virtual_ncidev.c:166
 __fput+0x3b7/0x890 fs/file_table.c:320
 task_work_run+0x246/0x300 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x6fb/0x2300 kernel/exit.c:869
 do_group_exit+0x202/0x2b0 kernel/exit.c:1019
 __do_sys_exit_group kernel/exit.c:1030 [inline]
 __se_sys_exit_group kernel/exit.c:1028 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1028
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe924ab7cb9
RSP: 002b:00007ffc4d4e0f88 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe924ab7cb9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007fe924b32290 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 00000000000000a0 R11: 0000000000000246 R12: 00007fe924b32290
R13: 0000000000000000 R14: 00007fe924b32d00 R15: 00007fe924a88e50
 </TASK>
INFO: task syz-executor136:3590 blocked for more than 143 seconds.
      Not tainted 6.1.45-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor136 state:D stack:26936 pid:3590  ppid:3538   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x132c/0x4330 kernel/sched/core.c:6554
 schedule+0xbf/0x180 kernel/sched/core.c:6630
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
 __mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 rfkill_fop_open+0x130/0x680 net/rfkill/core.c:1163
 misc_open+0x304/0x380 drivers/char/misc.c:143
 chrdev_open+0x54a/0x630 fs/char_dev.c:414
 do_dentry_open+0x7f9/0x10f0 fs/open.c:882
 do_open fs/namei.c:3557 [inline]
 path_openat+0x2644/0x2e60 fs/namei.c:3714
 do_filp_open+0x230/0x480 fs/namei.c:3741
 do_sys_openat2+0x13b/0x500 fs/open.c:1318
 do_sys_open fs/open.c:1334 [inline]
 __do_sys_openat fs/open.c:1350 [inline]
 __se_sys_openat fs/open.c:1345 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1345
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe924ab9b69
RSP: 002b:00007ffc4d4e0fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe924ab9b69
RDX: 0000000000000002 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 00000000000000a0 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000004c99a
R13: 00007ffc4d4e0ffc R14: 00007ffc4d4e1010 R15: 00007ffc4d4e1000
 </TASK>
INFO: task syz-executor136:3591 blocked for more than 144 seconds.
      Not tainted 6.1.45-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor136 state:D stack:26936 pid:3591  ppid:3533   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x132c/0x4330 kernel/sched/core.c:6554
 schedule+0xbf/0x180 kernel/sched/core.c:6630
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
 __mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 misc_open+0x58/0x380 drivers/char/misc.c:107
 chrdev_open+0x54a/0x630 fs/char_dev.c:414
 do_dentry_open+0x7f9/0x10f0 fs/open.c:882
 do_open fs/namei.c:3557 [inline]
 path_openat+0x2644/0x2e60 fs/namei.c:3714
 do_filp_open+0x230/0x480 fs/namei.c:3741
 do_sys_openat2+0x13b/0x500 fs/open.c:1318
 do_sys_open fs/open.c:1334 [inline]
 __do_sys_openat fs/open.c:1350 [inline]
 __se_sys_openat fs/open.c:1345 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1345
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe924ab9b69
RSP: 002b:00007ffc4d4e0fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe924ab9b69
RDX: 0000000000000002 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 00000000000000a0 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000004c9a4
R13: 00007ffc4d4e0ffc R14: 00007ffc4d4e1010 R15: 00007ffc4d4e1000
 </TASK>
INFO: task syz-executor136:3592 blocked for more than 144 seconds.
      Not tainted 6.1.45-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor136 state:D stack:27048 pid:3592  ppid:3537   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x132c/0x4330 kernel/sched/core.c:6554
 schedule+0xbf/0x180 kernel/sched/core.c:6630
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
 __mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 device_lock include/linux/device.h:836 [inline]
 nfc_dev_down net/nfc/core.c:143 [inline]
 nfc_rfkill_set_block+0x4c/0x2f0 net/nfc/core.c:179
 rfkill_set_block+0x1e7/0x430 net/rfkill/core.c:345
 rfkill_fop_write+0x5b7/0x790 net/rfkill/core.c:1286
 vfs_write+0x2d9/0xba0 fs/read_write.c:582
 ksys_write+0x19c/0x2c0 fs/read_write.c:637
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe924ab9b69
RSP: 002b:00007ffc4d4e0fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe924ab9b69
RDX: 0000000000000008 RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 00000000000f4240 R08: 00000000000000a0 R09: 00000000000000a0
R10: 00000000000000a0 R11: 0000000000000246 R12: 000000000004c9bc
R13: 00007ffc4d4e0ffc R14: 00007ffc4d4e1010 R15: 00007ffc4d4e1000
 </TASK>
INFO: task syz-executor136:3593 blocked for more than 144 seconds.
      Not tainted 6.1.45-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor136 state:D stack:27304 pid:3593  ppid:3534   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x132c/0x4330 kernel/sched/core.c:6554
 schedule+0xbf/0x180 kernel/sched/core.c:6630
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
 __mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 misc_open+0x58/0x380 drivers/char/misc.c:107
 chrdev_open+0x54a/0x630 fs/char_dev.c:414
 do_dentry_open+0x7f9/0x10f0 fs/open.c:882
 do_open fs/namei.c:3557 [inline]
 path_openat+0x2644/0x2e60 fs/namei.c:3714
 do_filp_open+0x230/0x480 fs/namei.c:3741
 do_sys_openat2+0x13b/0x500 fs/open.c:1318
 do_sys_open fs/open.c:1334 [inline]
 __do_sys_openat fs/open.c:1350 [inline]
 __se_sys_openat fs/open.c:1345 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1345
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe924ab9b69
RSP: 002b:00007ffc4d4e0fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe924ab9b69
RDX: 0000000000000002 RSI: 0000000020000540 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000004c99e
R13: 00007ffc4d4e0ffc R14: 00007ffc4d4e1010 R15: 00007ffc4d4e1000
 </TASK>
INFO: task syz-executor136:3594 blocked for more than 144 seconds.
      Not tainted 6.1.45-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor136 state:D stack:27192 pid:3594  ppid:3536   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x132c/0x4330 kernel/sched/core.c:6554
 schedule+0xbf/0x180 kernel/sched/core.c:6630
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
 __mutex_lock_common+0xe2b/0x2520 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
 misc_open+0x58/0x380 drivers/char/misc.c:107
 chrdev_open+0x54a/0x630 fs/char_dev.c:414
 do_dentry_open+0x7f9/0x10f0 fs/open.c:882
 do_open fs/namei.c:3557 [inline]
 path_openat+0x2644/0x2e60 fs/namei.c:3714
 do_filp_open+0x230/0x480 fs/namei.c:3741
 do_sys_openat2+0x13b/0x500 fs/open.c:1318
 do_sys_open fs/open.c:1334 [inline]
 __do_sys_openat fs/open.c:1350 [inline]
 __se_sys_openat fs/open.c:1345 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1345
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe924ab9b69
RSP: 002b:00007ffc4d4e0fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe924ab9b69
RDX: 0000000000000002 RSI: 0000000020000540 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000004c9be
R13: 00007ffc4d4e0ffc R14: 00007ffc4d4e1010 R15: 00007ffc4d4e1000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8d12a0b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8d12a8b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
 #0: ffffffff8d129ee0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3269:
 #0: ffff8880288f0098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2188
3 locks held by kworker/0:4/3570:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77a/0x11f0
 #1: ffffc90003c2fd20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x7bd/0x11f0 kernel/workqueue.c:2267
 #2: ffffffff8e549028 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
2 locks held by syz-executor136/3580:
 #0: ffff888079b7c100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
 #0: ffff888079b7c100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x5f/0x290 net/nfc/core.c:1165
 #1: ffffffff8e549028 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xcc/0x220 net/rfkill/core.c:1130
2 locks held by syz-executor136/3590:
 #0: ffffffff8d874028 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x58/0x380 drivers/char/misc.c:107
 #1: ffffffff8e549028 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_open+0x130/0x680 net/rfkill/core.c:1163
1 lock held by syz-executor136/3591:
 #0: ffffffff8d874028 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x58/0x380 drivers/char/misc.c:107
2 locks held by syz-executor136/3592:
 #0: ffffffff8e549028 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x1a5/0x790 net/rfkill/core.c:1278
 #1: ffff888079b7c100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
 #1: ffff888079b7c100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
 #1: ffff888079b7c100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x4c/0x2f0 net/nfc/core.c:179
1 lock held by syz-executor136/3593:
 #0: ffffffff8d874028 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x58/0x380 drivers/char/misc.c:107
1 lock held by syz-executor136/3594:
 #0: ffffffff8d874028 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x58/0x380 drivers/char/misc.c:107

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.45-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
 watchdog+0xf18/0xf60 kernel/hung_task.c:377
 kthread+0x26e/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 86 Comm: kworker/u4:4 Not tainted 6.1.45-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:arch_static_branch arch/x86/include/asm/jump_label.h:27 [inline]
RIP: 0010:static_key_false include/linux/jump_label.h:207 [inline]
RIP: 0010:native_write_msr arch/x86/include/asm/msr.h:147 [inline]
RIP: 0010:wrmsrl arch/x86/include/asm/msr.h:262 [inline]
RIP: 0010:native_x2apic_icr_write arch/x86/include/asm/apic.h:238 [inline]
RIP: 0010:__x2apic_send_IPI_dest arch/x86/kernel/apic/x2apic_phys.c:126 [inline]
RIP: 0010:x2apic_send_IPI+0x77/0xd0 arch/x86/kernel/apic/x2apic_phys.c:48
Code: 48 c1 e8 03 42 0f b6 04 38 84 c0 75 26 0f b7 13 0f ae f0 0f ae e8 41 83 fe 02 b8 00 04 00 00 41 0f 45 c6 b9 30 08 00 00 0f 30 <66> 90 5b 41 5e 41 5f 5d c3 89 d9 80 e1 07 fe c1 38 c1 7c cf 48 89
RSP: 0018:ffffc900020af4b8 EFLAGS: 00000206
RAX: 00000000000000fb RBX: ffff8880b98219b0 RCX: 0000000000000830
RDX: 0000000000000000 RSI: 00000000000000fb RDI: 0000000000000000
RBP: ffffffff8cb90850 R08: ffffffff817ee45d R09: ffffed10173275db
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92000415ea0 R14: 00000000000000fb R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005565058c9680 CR3: 000000000ce8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 arch_send_call_function_single_ipi arch/x86/include/asm/smp.h:109 [inline]
 send_call_function_single_ipi+0x188/0x260 kernel/sched/core.c:3782
 smp_call_function_many_cond+0x1ba3/0x33d0 kernel/smp.c:967
 on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1155
 on_each_cpu include/linux/smp.h:71 [inline]
 text_poke_sync arch/x86/kernel/alternative.c:1316 [inline]
 text_poke_bp_batch+0x5f9/0x940 arch/x86/kernel/alternative.c:1578
 text_poke_flush arch/x86/kernel/alternative.c:1707 [inline]
 text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1714
 arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
 static_key_disable_cpuslocked+0xca/0x1b0 kernel/jump_label.c:207
 static_key_disable+0x16/0x20 kernel/jump_label.c:215
 toggle_allocation_gate+0x3e0/0x480 mm/kfence/core.c:818
 process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292
 worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439
 kthread+0x26e/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.838 msecs

Crashes (64):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/08/15 04:03 linux-6.1.y 1321ab403b38 39990d51 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2024/01/15 00:46 linux-6.1.y 7c58bfa711cb 551587c1 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/06/03 08:18 linux-6.1.y d2869ace6eeb a4ae4f42 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/07/17 07:21 linux-6.1.y 61fd484b2cf6 35d9ecc5 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/06/30 15:08 linux-6.1.y a1c449d00ff8 01298212 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2024/04/18 21:49 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2024/04/06 03:38 linux-6.1.y 347385861c50 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2024/04/03 14:11 linux-6.1.y 347385861c50 7925100d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2024/02/22 08:55 linux-6.1.y 8b4118fabd6e 345111b5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2024/01/16 21:06 linux-6.1.y fec3b1451d5f 2a7bcc7f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/10/21 10:53 linux-6.1.y 7d24402875c7 361b23dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/09/13 15:40 linux-6.1.y 09045dae0d90 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2024/04/17 14:46 linux-6.1.y 6741e066ec76 acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/04/17 07:04 linux-6.1.y cd5d98c0556c 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/04/16 15:59 linux-6.1.y cd5d98c0556c 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/03/28 22:33 linux-6.1.y e5cd595e23c1 e91187ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/02/18 18:00 linux-6.1.y 8b4118fabd6e 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/02/12 17:31 linux-6.1.y f1bb70486c9c 77b23aa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/02/07 07:31 linux-6.1.y f1bb70486c9c 6404acf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/02/02 12:47 linux-6.1.y e5c3b988b827 d61103fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/01/20 14:34 linux-6.1.y 8fd7f4462453 9bd8dcda .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/01/14 06:04 linux-6.1.y 7c58bfa711cb 551587c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/10/11 01:17 linux-6.1.y 082280fe94a0 83165b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/10/08 04:07 linux-6.1.y ecda77b46871 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/10/07 08:26 linux-6.1.y ecda77b46871 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/10/04 15:04 linux-6.1.y d23900f974e0 b7d7ff54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/08/10 03:03 linux-6.1.y 0a4a7855302d 13ca4cd6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/08/04 21:26 linux-6.1.y 52a953d0934b cdae481e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/07/31 04:15 linux-6.1.y d2a6dc4eaf6d 2a0d0f29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/07/25 14:00 linux-6.1.y 5302e81aa209 3b91ad04 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/07/22 11:51 linux-6.1.y a456e1743881 27cbe77f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/07/05 14:52 linux-6.1.y 0f4ac6b4c5f0 80298b6f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/05/22 16:34 linux-6.1.y fa74641fb6b9 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/05/05 23:32 linux-6.1.y ca48fc16c493 de870ca5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/04/29 01:19 linux-6.1.y ca1c9012c941 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/04/18 03:44 linux-6.1.y 0102425ac76b 436577a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/03/24 01:20 linux-6.1.y e3a87a10f259 f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2023/08/24 19:59 linux-6.1.y 802aacbbffe2 49be837e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/08/19 18:53 linux-6.1.y 6c44e13dc284 d216d8a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/08/17 00:58 linux-6.1.y 6c44e13dc284 74b106b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/07/15 00:24 linux-6.1.y 61fd484b2cf6 35d9ecc5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/07/14 00:39 linux-6.1.y 61fd484b2cf6 55eda22f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/07/12 17:16 linux-6.1.y 61fd484b2cf6 979d5fe2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/07/08 12:09 linux-6.1.y 61fd484b2cf6 668cb1fa .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/07/06 07:28 linux-6.1.y 61fd484b2cf6 ba5dba36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/07/03 21:55 linux-6.1.y 0f4ac6b4c5f0 6e553898 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/06/30 02:12 linux-6.1.y a1c449d00ff8 01298212 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/06/28 07:14 linux-6.1.y e84a4e368abe 4cd5bb25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/06/26 16:32 linux-6.1.y e84a4e368abe 4cd5bb25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/06/19 16:46 linux-6.1.y ca87e77a2ef8 d521bc56 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/06/10 00:02 linux-6.1.y 2f3918bc53fb 9018a337 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/06/03 01:53 linux-6.1.y d2869ace6eeb a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/05/24 17:22 linux-6.1.y fa74641fb6b9 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/05/20 14:27 linux-6.1.y fa74641fb6b9 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/05/17 20:39 linux-6.1.y fa74641fb6b9 eaac4681 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/05/15 13:48 linux-6.1.y bf4ad6fa4e53 c4d362e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/05/08 23:42 linux-6.1.y ca48fc16c493 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/05/04 17:20 linux-6.1.y ca48fc16c493 518a39a6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/04/21 02:32 linux-6.1.y f17b0ab65d17 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/04/20 18:10 linux-6.1.y f17b0ab65d17 a219f34e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/03/25 09:53 linux-6.1.y e3a87a10f259 9700afae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/03/23 20:49 linux-6.1.y e3a87a10f259 f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/03/22 19:54 linux-6.1.y e3a87a10f259 f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/03/21 21:11 linux-6.1.y 7eaef76fbc46 8b4eb097 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in rfkill_global_led_trigger_worker
* Struck through repros no longer work on HEAD.