syzbot

 sign-in | mailing list | source | docs
🐞 Open [677]
🐞 Fixed [94]
🐞 Invalid [514]
⬇ Missing Backports [36]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

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: 610d, last: 7h48m
▶ ▼ Bug presence (1)
Date Name Commit Repro Result
2023/12/25 upstream (ToT) 861deac3b092 C [report] INFO: task hung in misc_open
▶ ▼ Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in rfkill_global_led_trigger_worker wireless 3 1092d 1128d 0/28 auto-closed as invalid on 2022/01/24 07:42
upstream INFO: task hung in rfkill_global_led_trigger_worker (3) wireless C 542 2h39m 125d 0/28 upstream: reported C repro on 2024/07/19 13:15
upstream INFO: task hung in rfkill_global_led_trigger_worker (2) net nfc C error 1362 135d 736d 26/28 fixed on 2024/07/09 19:14
linux-5.15 INFO: task hung in rfkill_global_led_trigger_worker origin:upstream C error 62 394d 623d 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 963d 1075d 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 OK (0) job log log
2023/12/25 10:42 1h33m bisect fix linux-6.1.y OK (0) job log log
2023/11/24 09:41 1h47m bisect fix linux-6.1.y OK (0) job log log

Sample crash report:
INFO: task kworker/0:3:3583 blocked for more than 143 seconds.
      Not tainted 6.1.116-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:3     state:D stack:28600 pid:3583  ppid:2      flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x143f/0x4570 kernel/sched/core.c:6558
 schedule+0xbf/0x180 kernel/sched/core.c:6634
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
 rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
 process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
 worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
 kthread+0x28d/0x320 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
INFO: task udevd:3623 blocked for more than 143 seconds.
      Not tainted 6.1.116-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd           state:D stack:24744 pid:3623  ppid:1      flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x143f/0x4570 kernel/sched/core.c:6558
 schedule+0xbf/0x180 kernel/sched/core.c:6634
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
 device_lock include/linux/device.h:837 [inline]
 uevent_show+0x176/0x330 drivers/base/core.c:2661
 dev_attr_show+0x50/0xb0 drivers/base/core.c:2364
 sysfs_kf_seq_show+0x32d/0x4b0 fs/sysfs/file.c:59
 seq_read_iter+0x43a/0xd10 fs/seq_file.c:230
 call_read_iter include/linux/fs.h:2259 [inline]
 new_sync_read fs/read_write.c:389 [inline]
 vfs_read+0x88d/0xbf0 fs/read_write.c:470
 ksys_read+0x19c/0x2c0 fs/read_write.c:613
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f9b93316b6a
RSP: 002b:00007fffdaf9b948 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 0000557ef8c47810 RCX: 00007f9b93316b6a
RDX: 0000000000001000 RSI: 0000557ef8c5bde0 RDI: 000000000000000c
RBP: 0000557ef8c47810 R08: 000000000000000c R09: 0000000000000400
R10: 000000000000010f R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000003fff R14: 00007fffdaf9be28 R15: 000000000000000a
 </TASK>
INFO: task syz-executor214:4271 blocked for more than 143 seconds.
      Not tainted 6.1.116-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor214 state:D stack:24856 pid:4271  ppid:4268   flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x143f/0x4570 kernel/sched/core.c:6558
 schedule+0xbf/0x180 kernel/sched/core.c:6634
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
 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:170
 __fput+0x3f6/0x8d0 fs/file_table.c:320
 task_work_run+0x246/0x300 kernel/task_work.c:203
 exit_task_work include/linux/task_work.h:39 [inline]
 do_exit+0xa73/0x26a0 kernel/exit.c:871
 do_group_exit+0x202/0x2b0 kernel/exit.c:1021
 __do_sys_exit_group kernel/exit.c:1032 [inline]
 __se_sys_exit_group kernel/exit.c:1030 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1030
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd14fb44cf9
RSP: 002b:00007ffdbf508958 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd14fb44cf9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007fd14fbbf290 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fd14fbbf290
R13: 0000000000000000 R14: 00007fd14fbbfd00 R15: 00007fd14fb15e80
 </TASK>
INFO: task syz-executor214:4282 blocked for more than 144 seconds.
      Not tainted 6.1.116-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor214 state:D stack:26656 pid:4282  ppid:4264   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x143f/0x4570 kernel/sched/core.c:6558
 schedule+0xbf/0x180 kernel/sched/core.c:6634
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
 device_lock include/linux/device.h:837 [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
 do_iter_write+0x503/0xc40 fs/read_write.c:863
 vfs_writev fs/read_write.c:934 [inline]
 do_writev+0x27b/0x460 fs/read_write.c:977
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd14fb46ba9
RSP: 002b:00007ffdbf5089b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd14fb46ba9
RDX: 0000000000000007 RSI: 0000000020000440 RDI: 0000000000000003
RBP: 00000000000f4240 R08: 00000000000000a0 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000224c3
R13: 00007ffdbf5089cc R14: 00007ffdbf5089e0 R15: 00007ffdbf5089d0
 </TASK>
INFO: task syz-executor214:4284 blocked for more than 144 seconds.
      Not tainted 6.1.116-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor214 state:D stack:27208 pid:4284  ppid:4269   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x143f/0x4570 kernel/sched/core.c:6558
 schedule+0xbf/0x180 kernel/sched/core.c:6634
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
 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:3626 [inline]
 path_openat+0x2644/0x2e60 fs/namei.c:3783
 do_filp_open+0x230/0x480 fs/namei.c:3810
 do_sys_openat2+0x13b/0x4f0 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:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd14fb46ba9
RSP: 002b:00007ffdbf5089b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd14fb46ba9
RDX: 0000000000000602 RSI: 00000000200000c0 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000224cb
R13: 00007ffdbf5089cc R14: 00007ffdbf5089e0 R15: 00007ffdbf5089d0
 </TASK>
INFO: task syz-executor214:4285 blocked for more than 144 seconds.
      Not tainted 6.1.116-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor214 state:D stack:27208 pid:4285  ppid:4267   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x143f/0x4570 kernel/sched/core.c:6558
 schedule+0xbf/0x180 kernel/sched/core.c:6634
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
 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:3626 [inline]
 path_openat+0x2644/0x2e60 fs/namei.c:3783
 do_filp_open+0x230/0x480 fs/namei.c:3810
 do_sys_openat2+0x13b/0x4f0 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:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd14fb46ba9
RSP: 002b:00007ffdbf5089b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd14fb46ba9
RDX: 0000000000000602 RSI: 00000000200000c0 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000224d7
R13: 00007ffdbf5089cc R14: 00007ffdbf5089e0 R15: 00007ffdbf5089d0
 </TASK>
INFO: task syz-executor214:4286 blocked for more than 144 seconds.
      Not tainted 6.1.116-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor214 state:D stack:27000 pid:4286  ppid:4265   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0x143f/0x4570 kernel/sched/core.c:6558
 schedule+0xbf/0x180 kernel/sched/core.c:6634
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
 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:3626 [inline]
 path_openat+0x2644/0x2e60 fs/namei.c:3783
 do_filp_open+0x230/0x480 fs/namei.c:3810
 do_sys_openat2+0x13b/0x4f0 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:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd14fb46ba9
RSP: 002b:00007ffdbf5089b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd14fb46ba9
RDX: 0000000000000602 RSI: 00000000200000c0 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000224c7
R13: 00007ffdbf5089cc R14: 00007ffdbf5089e0 R15: 00007ffdbf5089d0
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8d32b110 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8d32b910 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
 #0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 #0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
 #0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6510
3 locks held by kworker/0:3/3583:
 #0: ffff888017c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #1: ffffc9000e25fd20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
 #2: ffffffff8e7ab208 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
4 locks held by udevd/3623:
 #0: ffff88807e767790 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xae/0xd10 fs/seq_file.c:182
 #1: ffff888030b11c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x4f/0x3a0 fs/kernfs/file.c:154
 #2: ffff88801a2c8cb8 (kn->active#5){.+.+}-{0:0}, at: kernfs_seq_start+0x6e/0x3a0 fs/kernfs/file.c:155
 #3: ffff88801aa45100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
 #3: ffff88801aa45100 (&dev->mutex){....}-{3:3}, at: uevent_show+0x176/0x330 drivers/base/core.c:2661
2 locks held by getty/4011:
 #0: ffff88814cd26098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc900032462f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2198
2 locks held by syz-executor214/4271:
 #0: ffff88801aa45100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
 #0: ffff88801aa45100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x5f/0x290 net/nfc/core.c:1165
 #1: ffffffff8e7ab208 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xcc/0x220 net/rfkill/core.c:1130
2 locks held by syz-executor214/4282:
 #0: ffffffff8e7ab208 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x1a5/0x790 net/rfkill/core.c:1278
 #1: ffff88801aa45100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
 #1: ffff88801aa45100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
 #1: ffff88801aa45100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x4c/0x2f0 net/nfc/core.c:179
2 locks held by syz-executor214/4284:
 #0: ffffffff8da812a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x58/0x380 drivers/char/misc.c:107
 #1: ffffffff8e7ab208 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_open+0x130/0x680 net/rfkill/core.c:1163
1 lock held by syz-executor214/4285:
 #0: ffffffff8da812a8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x58/0x380 drivers/char/misc.c:107
1 lock held by syz-executor214/4286:
 #0: ffffffff8da812a8 (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.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
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+0x1ae/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+0xf88/0xfd0 kernel/hung_task.c:377
 kthread+0x28d/0x320 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 75 Comm: kworker/u4:4 Not tainted 6.1.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:native_write_cr3 arch/x86/include/asm/special_insns.h:54 [inline]
RIP: 0010:write_cr3 arch/x86/include/asm/special_insns.h:174 [inline]
RIP: 0010:load_new_mm_cr3 arch/x86/mm/tlb.c:293 [inline]
RIP: 0010:switch_mm_irqs_off+0x83c/0xc20 arch/x86/mm/tlb.c:628
Code: 48 8b 3b e9 33 03 00 00 e8 01 ef ff ff 41 0f b7 cf 81 f9 ff 0f 00 00 0f 83 22 01 00 00 41 8d 4f 01 0f b7 c9 48 09 c8 0f 22 d8 <48> c7 c6 ff ff ff ff 31 ff e8 d6 05 00 00 65 4c 89 25 0e c5 c5 7e
RSP: 0018:ffffc900020cf700 EFLAGS: 00000093
RAX: 0000000017c63000 RBX: ffff888017c68080 RCX: ffff888019b13b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900020cf7d0 R08: ffffffff813dcb68 R09: ffffed1002f8d08b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888017c68000
R13: 00000000000060ed R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f5bb4f1600 CR3: 0000000017c63000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 use_temporary_mm arch/x86/kernel/alternative.c:1065 [inline]
 __text_poke+0x59f/0x9a0 arch/x86/kernel/alternative.c:1176
 text_poke arch/x86/kernel/alternative.c:1240 [inline]
 text_poke_bp_batch+0x66b/0x940 arch/x86/kernel/alternative.c:1612
 text_poke_flush arch/x86/kernel/alternative.c:1725 [inline]
 text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1732
 arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
 static_key_disable_cpuslocked+0xce/0x1b0 kernel/jump_label.c:237
 static_key_disable+0x16/0x20 kernel/jump_label.c:245
 toggle_allocation_gate+0x3e0/0x480 mm/kfence/core.c:818
 process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
 worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
 kthread+0x28d/0x320 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.489 msecs

Crashes (118):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/11/11 08:06 linux-6.1.y d7039b844a1c 6b856513 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in rfkill_global_led_trigger_worker
2024/05/11 19:51 linux-6.1.y 909ba1f1b414 9026e142 .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/05/01 18:35 linux-6.1.y dcbc050cb0d3 3ba885bc .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/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/10/28 01:20 linux-6.1.y 7ec6f9fa3d97 65e8686b .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/10/26 14:40 linux-6.1.y 7ec6f9fa3d97 65e8686b .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/10/11 01:17 linux-6.1.y aa4cd140bba5 8fbfc0c8 .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/10/08 15:12 linux-6.1.y aa4cd140bba5 402f1df0 .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/09/17 12:11 linux-6.1.y 5f55cad62cc9 c673ca06 .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/09/15 03:33 linux-6.1.y 5f55cad62cc9 08d8a733 .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/09/10 21:31 linux-6.1.y 5ca5b389fddf 86aa7bd7 .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/09/09 22:14 linux-6.1.y 5ca5b389fddf 073f8be2 .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/08/22 15:54 linux-6.1.y ee5e09825b81 ca02180f .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/08/22 15:52 linux-6.1.y ee5e09825b81 ca02180f .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/08/05 22:14 linux-6.1.y 48d525b0e463 e35c337f .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/08/05 19:30 linux-6.1.y 48d525b0e463 e35c337f .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/08/02 07:09 linux-6.1.y c1cec4dad96b 1e9c4cf3 .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/07/12 10:12 linux-6.1.y 266ee8e06d5b eaeb5c15 .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/07/07 06:48 linux-6.1.y 7753af06eebf 2a40360c .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/07/06 04:30 linux-6.1.y 7753af06eebf 2a40360c .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/06/19 00:39 linux-6.1.y eb44d83053d6 639d6cdf .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/06/09 00:04 linux-6.1.y 88690811da69 82c05ab8 .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/06/01 07:21 linux-6.1.y 88690811da69 3113787f .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/05/25 21:22 linux-6.1.y 88690811da69 a10a183e .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/05/18 04:43 linux-6.1.y 4078fa637fcd c0f1611a .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/05/17 17:18 linux-6.1.y 4078fa637fcd a12e99e7 .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/05/01 09:16 linux-6.1.y dcbc050cb0d3 3ba885bc .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/27 03:03 linux-6.1.y 6741e066ec76 07b455f9 .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/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/11/21 08:10 linux-6.1.y b67dc5c9ade9 4b25d554 .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/11/09 11:14 linux-6.1.y d7039b844a1c 6b856513 .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/11/02 17:01 linux-6.1.y 7c15117f9468 f00eed24 .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/10/07 05:57 linux-6.1.y aa4cd140bba5 d7906eff .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/10/01 07:06 linux-6.1.y aa4cd140bba5 bbd4e0a4 .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/09/28 07:30 linux-6.1.y e526b12bf916 440b26ec .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/09/08 00:55 linux-6.1.y 699506173494 9750182a .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/07/12 18:03 linux-6.1.y 266ee8e06d5b eaeb5c15 .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/07/11 08:04 linux-6.1.y 7753af06eebf c699c2eb .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/07/02 03:50 linux-6.1.y 99e6a620de00 b294e901 .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/06/06 07:43 linux-6.1.y 88690811da69 121701b6 .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/05/25 00:55 linux-6.1.y 4078fa637fcd a10a183e .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/05/24 22:47 linux-6.1.y 4078fa637fcd a10a183e .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/05/22 04:58 linux-6.1.y 4078fa637fcd 1014eca7 .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/05/16 20:46 linux-6.1.y 909ba1f1b414 c2e07261 .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/05/15 09:31 linux-6.1.y 909ba1f1b414 94b087b1 .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/05/14 00:07 linux-6.1.y 909ba1f1b414 fdb4c10c .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/05/10 14:48 linux-6.1.y 909ba1f1b414 f7c35481 .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/05/10 00:45 linux-6.1.y 909ba1f1b414 de979bc2 .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/05/04 20:59 linux-6.1.y 909ba1f1b414 610f2a54 .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 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
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.