syzbot


INFO: task hung in rfkill_global_led_trigger_worker (2)

Status: upstream: reported C repro on 2022/11/15 16:56
Subsystems: wireless (incorrect?)
Reported-by: syzbot+2e39bc6569d281acbcfb@syzkaller.appspotmail.com
First crash: 136d, last: 1d05h

Cause bisection: failed (error log, bisect log)
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 3 490d 526d 0/24 auto-closed as invalid on 2022/01/24 07:42
linux-6.1 INFO: task hung in rfkill_global_led_trigger_worker 5 5d21h 9d10h 0/3 upstream: reported on 2023/03/21 21:11
linux-5.15 INFO: task hung in rfkill_global_led_trigger_worker 1 22d 22d 0/3 upstream: reported on 2023/03/08 16:06
linux-4.19 INFO: task hung in rfkill_global_led_trigger_worker 7 362d 474d 0/1 auto-closed as invalid on 2022/07/31 23:38
Last patch testing requests:
Created Duration User Patch Repo Result
2022/11/16 08:55 0m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git 9e4ce762f0e7 error
2022/11/16 05:12 25m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e01d50cbd6ee report log

Sample crash report:
INFO: task kworker/1:7:5123 blocked for more than 143 seconds.
      Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:7     state:D stack:29144 pid:5123  ppid:2      flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6690
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa48/0x1360 kernel/locking/mutex.c:747
 rfkill_global_led_trigger_worker+0x1b/0x120 net/rfkill/core.c:181
 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
 worker_thread+0x669/0x1090 kernel/workqueue.c:2436
 kthread+0x2e8/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
INFO: task syz-executor311:5597 blocked for more than 143 seconds.
      Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor311 state:D stack:27176 pid:5597  ppid:5075   flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6690
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa48/0x1360 kernel/locking/mutex.c:747
 rfkill_unregister+0xde/0x2c0 net/rfkill/core.c:1130
 nfc_unregister_device+0x96/0x330 net/nfc/core.c:1167
 virtual_ncidev_close+0x52/0xb0 drivers/nfc/virtual_ncidev.c:163
 __fput+0x27c/0xa90 fs/file_table.c:320
 task_work_run+0x16f/0x270 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xaa8/0x2950 kernel/exit.c:867
 do_group_exit+0xd4/0x2a0 kernel/exit.c:1010
 __do_sys_exit_group kernel/exit.c:1021 [inline]
 __se_sys_exit_group kernel/exit.c:1019 [inline]
 __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1019
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f146da6caf9
RSP: 002b:00007fff6094e078 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f146dae0330 RCX: 00007f146da6caf9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000000246 R12: 00007f146dae0330
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
 </TASK>
INFO: task syz-executor311:5600 blocked for more than 143 seconds.
      Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor311 state:D stack:26896 pid:5600  ppid:5080   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6690
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa48/0x1360 kernel/locking/mutex.c:747
 device_lock include/linux/device.h:831 [inline]
 nfc_dev_down+0x2d/0x2d0 net/nfc/core.c:143
 nfc_rfkill_set_block+0x33/0xd0 net/nfc/core.c:179
 rfkill_set_block+0x1f9/0x540 net/rfkill/core.c:345
 rfkill_fop_write+0x2c7/0x570 net/rfkill/core.c:1286
 vfs_write+0x2db/0xdd0 fs/read_write.c:582
 ksys_write+0x1ec/0x250 fs/read_write.c:637
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f146da6de69
RSP: 002b:00007fff6094e0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000000f4240 RCX: 00007f146da6de69
RDX: 0000000000000008 RSI: 0000000020000080 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000000246 R12: 000000000000e920
R13: 00007fff6094e0dc R14: 00007fff6094e0f0 R15: 00007fff6094e0e0
 </TASK>
INFO: task syz-executor311:5603 blocked for more than 144 seconds.
      Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor311 state:D stack:27288 pid:5603  ppid:5079   flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6690
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa48/0x1360 kernel/locking/mutex.c:747
 rfkill_unregister+0xde/0x2c0 net/rfkill/core.c:1130
 nfc_unregister_device+0x96/0x330 net/nfc/core.c:1167
 virtual_ncidev_close+0x52/0xb0 drivers/nfc/virtual_ncidev.c:163
 __fput+0x27c/0xa90 fs/file_table.c:320
 task_work_run+0x16f/0x270 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xaa8/0x2950 kernel/exit.c:867
 do_group_exit+0xd4/0x2a0 kernel/exit.c:1010
 __do_sys_exit_group kernel/exit.c:1021 [inline]
 __se_sys_exit_group kernel/exit.c:1019 [inline]
 __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1019
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f146da6caf9
RSP: 002b:00007fff6094e078 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f146dae0330 RCX: 00007f146da6caf9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000000246 R12: 00007f146dae0330
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
 </TASK>
INFO: task syz-executor311:5625 blocked for more than 144 seconds.
      Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor311 state:D stack:26784 pid:5625  ppid:5077   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6690
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa48/0x1360 kernel/locking/mutex.c:747
 rfkill_register+0x3a/0xb00 net/rfkill/core.c:1057
 nfc_register_device+0x124/0x3b0 net/nfc/core.c:1132
 nci_register_device+0x7cb/0xb50 net/nfc/nci/core.c:1257
 virtual_ncidev_open+0x14f/0x230 drivers/nfc/virtual_ncidev.c:148
 misc_open+0x37a/0x4a0 drivers/char/misc.c:165
 chrdev_open+0x26a/0x770 fs/char_dev.c:414
 do_dentry_open+0x6cc/0x13f0 fs/open.c:882
 do_open fs/namei.c:3557 [inline]
 path_openat+0x1bbc/0x2a50 fs/namei.c:3714
 do_filp_open+0x1ba/0x410 fs/namei.c:3741
 do_sys_openat2+0x16d/0x4c0 fs/open.c:1310
 do_sys_open fs/open.c:1326 [inline]
 __do_sys_openat fs/open.c:1342 [inline]
 __se_sys_openat fs/open.c:1337 [inline]
 __x64_sys_openat+0x143/0x1f0 fs/open.c:1337
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f146da6de69
RSP: 002b:00007fff6094e0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00000000000f4240 RCX: 00007f146da6de69
RDX: 0000000000000002 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 0000000000000000 R08: 00007fff6094db40 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000e988
R13: 00007fff6094e0dc R14: 00007fff6094e0f0 R15: 00007fff6094e0e0
 </TASK>
INFO: task syz-executor311:5630 blocked for more than 144 seconds.
      Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor311 state:D stack:27968 pid:5630  ppid:5078   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6690
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa48/0x1360 kernel/locking/mutex.c:747
 misc_open+0x63/0x4a0 drivers/char/misc.c:129
 chrdev_open+0x26a/0x770 fs/char_dev.c:414
 do_dentry_open+0x6cc/0x13f0 fs/open.c:882
 do_open fs/namei.c:3557 [inline]
 path_openat+0x1bbc/0x2a50 fs/namei.c:3714
 do_filp_open+0x1ba/0x410 fs/namei.c:3741
 do_sys_openat2+0x16d/0x4c0 fs/open.c:1310
 do_sys_open fs/open.c:1326 [inline]
 __do_sys_openat fs/open.c:1342 [inline]
 __se_sys_openat fs/open.c:1337 [inline]
 __x64_sys_openat+0x143/0x1f0 fs/open.c:1337
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f146da6de69
RSP: 002b:00007fff6094e0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00000000000f4240 RCX: 00007f146da6de69
RDX: 0000000000000002 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 0000000000000000 R08: 00007fff6094db40 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000e9b2
R13: 00007fff6094e0dc R14: 00007fff6094e0f0 R15: 00007fff6094e0e0
 </TASK>
INFO: task syz-executor311:5631 blocked for more than 144 seconds.
      Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor311 state:D stack:28240 pid:5631  ppid:5074   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5244 [inline]
 __schedule+0xb8a/0x5450 kernel/sched/core.c:6555
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6690
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0xa48/0x1360 kernel/locking/mutex.c:747
 misc_open+0x63/0x4a0 drivers/char/misc.c:129
 chrdev_open+0x26a/0x770 fs/char_dev.c:414
 do_dentry_open+0x6cc/0x13f0 fs/open.c:882
 do_open fs/namei.c:3557 [inline]
 path_openat+0x1bbc/0x2a50 fs/namei.c:3714
 do_filp_open+0x1ba/0x410 fs/namei.c:3741
 do_sys_openat2+0x16d/0x4c0 fs/open.c:1310
 do_sys_open fs/open.c:1326 [inline]
 __do_sys_openat fs/open.c:1342 [inline]
 __se_sys_openat fs/open.c:1337 [inline]
 __x64_sys_openat+0x143/0x1f0 fs/open.c:1337
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f146da6de69
RSP: 002b:00007fff6094e0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00000000000f4240 RCX: 00007f146da6de69
RDX: 0000000000000002 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 0000000000000000 R08: 00007fff6094db40 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000e9c0
R13: 00007fff6094e0dc R14: 00007fff6094e0f0 R15: 00007fff6094e0e0
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8c790c70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8c790970 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
1 lock held by khungtaskd/28:
 #0: ffffffff8c7917c0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x57/0x264 kernel/locking/lockdep.c:6494
2 locks held by getty/4752:
 #0: ffff888027bf2098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x26/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffffc900015902f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef4/0x13e0 drivers/tty/n_tty.c:2177
3 locks held by kworker/1:7/5123:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1280 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:636 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:663 [inline]
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x86d/0x1710 kernel/workqueue.c:2260
 #1: ffffc90003e7fda8 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x8a1/0x1710 kernel/workqueue.c:2264
 #2: ffffffff8e4e4328 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x1b/0x120 net/rfkill/core.c:181
2 locks held by syz-executor311/5597:
 #0: ffff88807c979100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:831 [inline]
 #0: ffff88807c979100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x62/0x330 net/nfc/core.c:1165
 #1: ffffffff8e4e4328 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xde/0x2c0 net/rfkill/core.c:1130
2 locks held by syz-executor311/5600:
 #0: ffffffff8e4e4328 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x160/0x570 net/rfkill/core.c:1278
 #1: ffff88807c979100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:831 [inline]
 #1: ffff88807c979100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down+0x2d/0x2d0 net/nfc/core.c:143
2 locks held by syz-executor311/5603:
 #0: ffff888078e25100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:831 [inline]
 #0: ffff888078e25100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x62/0x330 net/nfc/core.c:1165
 #1: ffffffff8e4e4328 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xde/0x2c0 net/rfkill/core.c:1130
3 locks held by syz-executor311/5625:
 #0: ffffffff8d244ec8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x63/0x4a0 drivers/char/misc.c:129
 #1: ffff88807d50a100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:831 [inline]
 #1: ffff88807d50a100 (&dev->mutex){....}-{3:3}, at: nfc_register_device+0x9f/0x3b0 net/nfc/core.c:1128
 #2: ffffffff8e4e4328 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x3a/0xb00 net/rfkill/core.c:1057
1 lock held by syz-executor311/5630:
 #0: ffffffff8d244ec8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x63/0x4a0 drivers/char/misc.c:129
1 lock held by syz-executor311/5631:
 #0: ffffffff8d244ec8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x63/0x4a0 drivers/char/misc.c:129

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

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106
 nmi_cpu_backtrace.cold+0x24/0x18a lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x333/0x3c0 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+0xc75/0xfc0 kernel/hung_task.c:377
 kthread+0x2e8/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 1052 Comm: kworker/u4:6 Not tainted 6.1.0-syzkaller-13872-gb6bb9676f216 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:dequeue_task_fair+0x11d/0xfc0 kernel/sched/fair.c:6157
Code: b8 00 00 00 00 00 fc ff df 48 c1 ea 03 0f b6 04 02 84 c0 74 08 3c 03 0f 8e b3 0b 00 00 48 8d b5 7c 01 00 00 8b 85 78 01 00 00 <48> ba 00 00 00 00 00 fc ff df 48 89 f1 48 89 74 24 20 83 e6 07 48
RSP: 0018:ffffc9000558fa10 EFLAGS: 00000046
RAX: 00000000000001a0 RBX: 0000000000000000 RCX: ffff8880b983b65c
RDX: 1ffff110040073d7 RSI: ffff888020039ebc RDI: ffff88802003a14c
RBP: ffff888020039d40 R08: ffff8880b983bfc8 R09: ffff8880b983c000
R10: fffffbfff1ce5b5a R11: ffff8880b983c158 R12: ffff88802003a210
R13: ffff8880b983b580 R14: 0000000000000000 R15: ffff888020039d40
FS:  0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000556a3d053bf8 CR3: 000000000c48e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 dequeue_task kernel/sched/core.c:2080 [inline]
 deactivate_task kernel/sched/core.c:2094 [inline]
 __schedule+0x1341/0x5450 kernel/sched/core.c:6509
 schedule+0xde/0x1b0 kernel/sched/core.c:6631
 toggle_allocation_gate mm/kfence/core.c:801 [inline]
 toggle_allocation_gate+0x1ad/0x230 mm/kfence/core.c:791
 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
 worker_thread+0x669/0x1090 kernel/workqueue.c:2436
 kthread+0x2e8/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

Crashes (263):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce 2022/12/21 05:56 upstream b6bb9676f216 d3e76707 .config strace log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-smack-root 2022/12/20 22:58 upstream 6feb57c2fd7c d3e76707 .config strace log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci2-upstream-fs 2022/11/28 22:06 upstream b7b275e60bcd 247de55b .config strace log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2022/11/27 15:21 upstream faf68e3523c2 74a66371 .config strace log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-root 2022/11/27 03:15 upstream 644e9524388a 74a66371 .config strace log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci2-upstream-fs 2022/11/15 12:21 upstream e01d50cbd6ee 97de9cfc .config strace log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2022/12/02 13:38 upstream 355479c70a48 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2022/11/16 12:45 upstream 81e7cfa3a9eb 3a127a31 .config console log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-linux-next-kasan-gce-root 2023/02/24 01:09 linux-next 0222aa9800b2 9e2ebb3c .config strace log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-linux-next-kasan-gce-root 2023/01/13 04:47 linux-next 0a093b2893c7 96166539 .config strace log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-linux-next-kasan-gce-root 2022/12/26 15:45 linux-next c76083fac3ba 9da18ae8 .config console log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2022/11/27 21:23 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6d464646530f 74a66371 .config console log report syz C [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/30 01:51 upstream ffe78bbd5121 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-selinux-root 2023/03/29 22:28 upstream ffe78bbd5121 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/29 02:13 upstream fcd476ea6a88 fc067f05 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/28 15:09 upstream 3a93e40326c8 48c74771 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-smack-root 2023/03/27 12:58 upstream 197b6b60ae7b f8f96aa9 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/26 10:31 upstream da8e7da11e4b fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci2-upstream-fs 2023/03/26 00:47 upstream da8e7da11e4b fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-root 2023/03/25 11:08 upstream 65aca32efdcb fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/24 19:34 upstream 4bae0ad148f4 9700afae .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-selinux-root 2023/03/23 11:00 upstream fff5a5e7f528 f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-smack-root 2023/03/23 02:30 upstream fff5a5e7f528 f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-selinux-root 2023/03/22 02:51 upstream 2faac9a98f01 8b4eb097 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-smack-root 2023/03/17 18:21 upstream 38e04b3e4240 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-root 2023/03/16 22:23 upstream 0ddc84d2dd43 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/14 11:54 upstream fc89d7fb499b 0d5c4377 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-root 2023/03/14 00:52 upstream fc89d7fb499b 026e2200 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/13 21:38 upstream fc89d7fb499b 026e2200 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/13 08:42 upstream eeac8ede1755 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-root 2023/03/12 20:52 upstream 134231664868 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-smack-root 2023/03/05 06:42 upstream b01fe98d34f3 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-selinux-root 2023/03/04 06:17 upstream 0a3f9a6b0265 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/03/04 01:04 upstream 0a3f9a6b0265 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-root 2023/02/28 01:13 upstream 982818426a0f e792ae78 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-smack-root 2023/02/26 04:29 upstream 1ec35eadc3b4 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-selinux-root 2023/02/23 22:55 upstream a5c95ca18a98 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce 2023/02/23 05:03 upstream d8ca6dbb8de7 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-root 2023/02/22 15:14 upstream 5b7c4cabbb65 409945bc .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/29 03:30 upstream fcd476ea6a88 fc067f05 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/27 01:04 upstream 0ec57cfa721f fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/24 18:31 upstream 1e760fa3596e 9700afae .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/22 15:18 upstream a1effab7a3a3 d846e076 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-qemu2-arm32 2023/03/22 04:12 upstream 2faac9a98f01 8b4eb097 .config console log report info INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/19 22:06 upstream 5cdfdd6da323 7939252e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/19 03:27 upstream a3671bd86a97 7939252e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/17 13:03 upstream 38e04b3e4240 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-qemu2-arm32 2023/03/17 08:18 upstream 38e04b3e4240 18b58603 .config console log report info INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/13 10:46 upstream eeac8ede1755 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/04 15:52 upstream 0988a0ea7919 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/03/02 04:21 upstream ee3f96b16468 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/02/27 11:29 upstream f3a2439f20d9 e792ae78 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/02/23 16:39 upstream d8ca6dbb8de7 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2023/02/23 08:03 upstream d8ca6dbb8de7 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-kasan-gce-386 2022/11/14 15:19 upstream 094226ad94f4 943f4cb8 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-linux-next-kasan-gce-root 2023/03/28 09:27 linux-next a6faf7ea9fcb 47f3aaf1 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-linux-next-kasan-gce-root 2023/02/27 02:56 linux-next 7f7a8831520f ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2023/03/27 11:29 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e8d018dd0257 f8f96aa9 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2023/03/21 11:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e 03fb9538 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2023/03/15 14:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2023/03/09 01:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e 4fc6d98d .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2023/03/07 20:16 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e ffaa5c55 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2023/02/28 17:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2ebd1fbb946d 95aee97a .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2023/02/24 18:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2ebd1fbb946d ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
ci-upstream-gce-arm64 2023/02/21 22:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a9b06ec42c0f 42a4d508 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in rfkill_global_led_trigger_worker
* Struck through repros no longer work on HEAD.