syzbot


INFO: task hung in rfkill_global_led_trigger_worker (2)

Status: upstream: reported C repro on 2022/11/15 16:56
Subsystems: net nfc
[Documentation on labels]
Reported-by: syzbot+2e39bc6569d281acbcfb@syzkaller.appspotmail.com
First crash: 551d, last: 39m
Cause bisection: failed (error log, bisect log)
  
Discussions (21)
Title Replies (including bot) Last reply
[syzbot] Monthly net report (Apr 2024) 0 (1) 2024/04/30 07:11
[syzbot] Monthly nfc report (Apr 2024) 0 (1) 2024/04/15 09:23
[syzbot] Monthly net report (Mar 2024) 0 (1) 2024/03/29 18:37
[syzbot] Monthly nfc report (Mar 2024) 0 (1) 2024/03/14 09:23
[syzbot] Monthly net report (Feb 2024) 0 (1) 2024/02/27 09:32
[syzbot] Monthly nfc report (Feb 2024) 0 (1) 2024/02/12 10:26
[syzbot] Monthly net report (Jan 2024) 0 (1) 2024/01/26 21:54
[syzbot] Monthly nfc report (Jan 2024) 0 (1) 2024/01/12 00:04
[syzbot] Monthly net report (Dec 2023) 0 (1) 2023/12/27 09:18
[syzbot] Monthly nfc report (Dec 2023) 0 (1) 2023/12/11 13:29
[syzbot] Monthly nfc report (Nov 2023) 0 (1) 2023/11/10 06:20
[syzbot] Monthly nfc report (Oct 2023) 0 (1) 2023/10/09 12:45
[syzbot] Monthly nfc report (Sep 2023) 0 (1) 2023/09/06 08:12
[syzbot] Monthly wireless report (May 2023) 0 (1) 2023/05/26 09:38
[syzbot] Monthly wireless report 0 (1) 2023/04/24 17:33
[syzbot] [wireless] Monthly Report 0 (1) 2023/03/24 15:33
[PATCH] drivers/core: Replace lockdep_set_novalidate_class() with unique class keys 47 (47) 2023/02/20 17:32
Converting dev->mutex into dev->spinlock ? 29 (29) 2023/02/08 00:34
[perf] lockdep warning between cpu_add_remove_lock and &dev->mutex. 5 (5) 2023/01/23 15:28
Re: [syzbot] INFO: task hung in rfkill_global_led_trigger_worker (2) 1 (1) 2022/11/16 09:27
[syzbot] INFO: task hung in rfkill_global_led_trigger_worker (2) 0 (1) 2022/11/15 16:56
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 905d 941d 0/26 auto-closed as invalid on 2022/01/24 07:42
linux-6.1 INFO: task hung in rfkill_global_led_trigger_worker origin:upstream C 80 20h42m 424d 0/3 upstream: reported C repro on 2023/03/21 21:11
linux-5.15 INFO: task hung in rfkill_global_led_trigger_worker origin:upstream C error 62 208d 437d 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 777d 888d 0/1 auto-closed as invalid on 2022/07/31 23:38
Last patch testing requests (12)
Created Duration User Patch Repo Result
2023/11/20 07:01 27m retest repro upstream report log
2023/11/20 07:01 26m retest repro upstream report log
2023/11/20 07:01 16m retest repro upstream report log
2023/11/20 07:01 15m retest repro upstream report log
2023/11/20 07:01 28m retest repro linux-next report log
2023/11/20 06:00 37m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2023/11/20 06:00 22m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2023/11/20 03:43 28m retest repro upstream report log
2023/11/20 03:43 22m retest repro upstream report log
2023/11/20 03:43 29m retest repro upstream report log
2022/11/16 08:55 0m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git 9e4ce762f0e7 error OK
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:17:5325 blocked for more than 143 seconds.
      Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:17    state:D stack:27816 pid:5325  ppid:2      flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6845
 __mutex_lock_common+0xe33/0x2530 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 rfkill_global_led_trigger_worker+0x27/0xd0 net/rfkill/core.c:181
 process_one_work+0x92c/0x12c0 kernel/workqueue.c:2600
 worker_thread+0xa63/0x1210 kernel/workqueue.c:2751
 kthread+0x2b8/0x350 kernel/kthread.c:389
 ret_from_fork+0x2e/0x60 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
 </TASK>
INFO: task syz-executor210:5510 blocked for more than 143 seconds.
      Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor210 state:D stack:25608 pid:5510  ppid:5027   flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6845
 __mutex_lock_common+0xe33/0x2530 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 rfkill_unregister+0xd0/0x230 net/rfkill/core.c:1130
 nfc_unregister_device+0x96/0x2a0 net/nfc/core.c:1167
 virtual_ncidev_close+0x59/0x90 drivers/nfc/virtual_ncidev.c:163
 __fput+0x3f8/0x950 fs/file_table.c:384
 task_work_run+0x24a/0x300 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x68f/0x2290 kernel/exit.c:874
 do_group_exit+0x206/0x2c0 kernel/exit.c:1024
 __do_sys_exit_group kernel/exit.c:1035 [inline]
 __se_sys_exit_group kernel/exit.c:1033 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1033
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fde46f78c79
RSP: 002b:00007fff26212e88 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fde46f78c79
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007fde46ff3290 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 00000000000000a0 R11: 0000000000000246 R12: 00007fde46ff3290
R13: 0000000000000000 R14: 00007fde46ff3d00 R15: 00007fde46f49e30
 </TASK>
INFO: task syz-executor210:5511 blocked for more than 143 seconds.
      Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor210 state:D stack:25832 pid:5511  ppid:5024   flags:0x00004002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6845
 __mutex_lock_common+0xe33/0x2530 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 rfkill_fop_release+0x4d/0x230 net/rfkill/core.c:1312
 __fput+0x3f8/0x950 fs/file_table.c:384
 task_work_run+0x24a/0x300 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x68f/0x2290 kernel/exit.c:874
 do_group_exit+0x206/0x2c0 kernel/exit.c:1024
 __do_sys_exit_group kernel/exit.c:1035 [inline]
 __se_sys_exit_group kernel/exit.c:1033 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1033
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fde46f78c79
RSP: 002b:00007fff26212e88 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fde46f78c79
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007fde46ff3290 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 00000000000000a0 R11: 0000000000000246 R12: 00007fde46ff3290
R13: 0000000000000000 R14: 00007fde46ff3d00 R15: 00007fde46f49e30
 </TASK>
INFO: task syz-executor210:5512 blocked for more than 144 seconds.
      Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor210 state:D stack:25896 pid:5512  ppid:5023   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6845
 __mutex_lock_common+0xe33/0x2530 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 device_lock include/linux/device.h:958 [inline]
 nfc_dev_down net/nfc/core.c:143 [inline]
 nfc_rfkill_set_block+0x50/0x300 net/nfc/core.c:179
 rfkill_set_block+0x1e7/0x430 net/rfkill/core.c:345
 rfkill_fop_write+0x5bb/0x790 net/rfkill/core.c:1286
 vfs_write+0x286/0xaf0 fs/read_write.c:582
 ksys_write+0x1a0/0x2c0 fs/read_write.c:637
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fde46f7ab29
RSP: 002b:00007fff26212ee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fde46f7ab29
RDX: 0000000000000008 RSI: 00000000200000c0 RDI: 0000000000000004
RBP: 00000000000f4240 R08: 00000000000000a0 R09: 00000000000000a0
R10: 00000000000000a0 R11: 0000000000000246 R12: 0000000000012365
R13: 00007fff26212efc R14: 00007fff26212f10 R15: 00007fff26212f00
 </TASK>
INFO: task syz-executor210:5537 blocked for more than 144 seconds.
      Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor210 state:D stack:24824 pid:5537  ppid:5022   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6845
 __mutex_lock_common+0xe33/0x2530 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 rfkill_register+0x34/0x880 net/rfkill/core.c:1057
 nfc_register_device+0x148/0x320 net/nfc/core.c:1132
 nci_register_device+0x7c2/0x900 net/nfc/nci/core.c:1257
 virtual_ncidev_open+0x13c/0x1b0 drivers/nfc/virtual_ncidev.c:148
 misc_open+0x30b/0x380 drivers/char/misc.c:165
 chrdev_open+0x551/0x630 fs/char_dev.c:414
 do_dentry_open+0x829/0x1470 fs/open.c:914
 do_open fs/namei.c:3636 [inline]
 path_openat+0x27bb/0x3180 fs/namei.c:3793
 do_filp_open+0x234/0x490 fs/namei.c:3820
 do_sys_openat2+0x13e/0x1d0 fs/open.c:1407
 do_sys_open fs/open.c:1422 [inline]
 __do_sys_openat fs/open.c:1438 [inline]
 __se_sys_openat fs/open.c:1433 [inline]
 __x64_sys_openat+0x247/0x290 fs/open.c:1433
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fde46f7ab29
RSP: 002b:00007fff26212ee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fde46f7ab29
RDX: 0000000000000002 RSI: 0000000020000540 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000012482
R13: 00007fff26212efc R14: 00007fff26212f10 R15: 00007fff26212f00
 </TASK>
INFO: task syz-executor210:5538 blocked for more than 144 seconds.
      Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor210 state:D stack:27272 pid:5538  ppid:5026   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6845
 __mutex_lock_common+0xe33/0x2530 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 misc_open+0x5c/0x380 drivers/char/misc.c:129
 chrdev_open+0x551/0x630 fs/char_dev.c:414
 do_dentry_open+0x829/0x1470 fs/open.c:914
 do_open fs/namei.c:3636 [inline]
 path_openat+0x27bb/0x3180 fs/namei.c:3793
 do_filp_open+0x234/0x490 fs/namei.c:3820
 do_sys_openat2+0x13e/0x1d0 fs/open.c:1407
 do_sys_open fs/open.c:1422 [inline]
 __do_sys_openat fs/open.c:1438 [inline]
 __se_sys_openat fs/open.c:1433 [inline]
 __x64_sys_openat+0x247/0x290 fs/open.c:1433
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fde46f7ab29
RSP: 002b:00007fff26212ee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fde46f7ab29
RDX: 0000000000000002 RSI: 0000000020000540 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000012482
R13: 00007fff26212efc R14: 00007fff26212f10 R15: 00007fff26212f00
 </TASK>
INFO: task syz-executor210:5539 blocked for more than 144 seconds.
      Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor210 state:D stack:26280 pid:5539  ppid:5028   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6845
 __mutex_lock_common+0xe33/0x2530 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 misc_open+0x5c/0x380 drivers/char/misc.c:129
 chrdev_open+0x551/0x630 fs/char_dev.c:414
 do_dentry_open+0x829/0x1470 fs/open.c:914
 do_open fs/namei.c:3636 [inline]
 path_openat+0x27bb/0x3180 fs/namei.c:3793
 do_filp_open+0x234/0x490 fs/namei.c:3820
 do_sys_openat2+0x13e/0x1d0 fs/open.c:1407
 do_sys_open fs/open.c:1422 [inline]
 __do_sys_openat fs/open.c:1438 [inline]
 __se_sys_openat fs/open.c:1433 [inline]
 __x64_sys_openat+0x247/0x290 fs/open.c:1433
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fde46f7ab29
RSP: 002b:00007fff26212ee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fde46f7ab29
RDX: 0000000000000002 RSI: 0000000020000540 RDI: ffffffffffffff9c
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000001247a
R13: 00007fff26212efc R14: 00007fff26212f10 R15: 00007fff26212f00
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8d3295b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:522
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8d329970 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:522
1 lock held by khungtaskd/28:
 #0: ffffffff8d3293e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
1 lock held by klogd/4459:
 #0: ffff8880b983bf98 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:558
2 locks held by getty/4766:
 #0: ffff88802d5ba098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015b02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6b1/0x1dc0 drivers/tty/n_tty.c:2187
3 locks held by kworker/1:17/5325:
 #0: ffff888012870d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7e3/0x12c0 kernel/workqueue.c:2572
 #1: ffffc90004cdfd00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x82b/0x12c0 kernel/workqueue.c:2574
 #2: ffffffff8e7841c8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x27/0xd0 net/rfkill/core.c:181
2 locks held by syz-executor210/5510:
 #0: ffff888015efd100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:958 [inline]
 #0: ffff888015efd100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x63/0x2a0 net/nfc/core.c:1165
 #1: ffffffff8e7841c8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xd0/0x230 net/rfkill/core.c:1130
1 lock held by syz-executor210/5511:
 #0: ffffffff8e7841c8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_release+0x4d/0x230 net/rfkill/core.c:1312
2 locks held by syz-executor210/5512:
 #0: ffffffff8e7841c8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x1a9/0x790 net/rfkill/core.c:1278
 #1: ffff888015efd100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:958 [inline]
 #1: ffff888015efd100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
 #1: ffff888015efd100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x300 net/nfc/core.c:179
3 locks held by syz-executor210/5537:
 #0: ffffffff8da702e8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5c/0x380 drivers/char/misc.c:129
 #1: ffff88807d697100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:958 [inline]
 #1: ffff88807d697100 (&dev->mutex){....}-{3:3}, at: nfc_register_device+0x9c/0x320 net/nfc/core.c:1128
 #2: ffffffff8e7841c8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x34/0x880 net/rfkill/core.c:1057
1 lock held by syz-executor210/5538:
 #0: ffffffff8da702e8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5c/0x380 drivers/char/misc.c:129
1 lock held by syz-executor210/5539:
 #0: ffffffff8da702e8 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x5c/0x380 drivers/char/misc.c:129

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

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #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+0x1e7/0x2d0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x498/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x187/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xec2/0xf00 kernel/hung_task.c:379
 kthread+0x2b8/0x350 kernel/kthread.c:389
 ret_from_fork+0x2e/0x60 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 1146 Comm: kworker/u4:5 Not tainted 6.5.0-rc6-syzkaller-00027-g91aa6c412d7f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:19 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:67 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:127 [inline]
RIP: 0010:__text_poke+0x7ae/0x9b0 arch/x86/kernel/alternative.c:1875
Code: 02 00 00 4c 8d b4 24 20 01 00 00 4c 8b 7c 24 68 41 f7 c7 00 02 00 00 74 05 e8 9e b4 60 00 4c 89 f3 48 c1 eb 03 42 80 3c 23 00 <74> 08 4c 89 f7 e8 98 c6 b2 00 48 c7 84 24 20 01 00 00 00 00 00 00
RSP: 0018:ffffc900058077e0 EFLAGS: 00000046
RAX: eae69f112c3bdd00 RBX: 1ffff92000b00f20 RCX: ffffffff816bdd8a
RDX: dffffc0000000000 RSI: ffffffff8b0a97e0 RDI: ffffffff8b58ad20
RBP: ffffc900058079b0 R08: ffffffff907b4307 R09: 1ffffffff20f6860
R10: dffffc0000000000 R11: fffffbfff20f6861 R12: dffffc0000000000
R13: 1ffff92000b00f0c R14: ffffc90005807900 R15: 0000000000000246
FS:  0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000560b2a9ac600 CR3: 000000000d130000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 text_poke arch/x86/kernel/alternative.c:1900 [inline]
 text_poke_bp_batch+0x687/0x960 arch/x86/kernel/alternative.c:2289
 text_poke_flush arch/x86/kernel/alternative.c:2402 [inline]
 text_poke_finish+0x1a/0x30 arch/x86/kernel/alternative.c:2409
 arch_jump_label_transform_apply+0x17/0x30 arch/x86/kernel/jump_label.c:146
 static_key_disable_cpuslocked+0xce/0x1b0 kernel/jump_label.c:235
 static_key_disable+0x1a/0x20 kernel/jump_label.c:243
 toggle_allocation_gate+0x1b8/0x250 mm/kfence/core.c:836
 process_one_work+0x92c/0x12c0 kernel/workqueue.c:2600
 worker_thread+0xa63/0x1210 kernel/workqueue.c:2751
 kthread+0x2b8/0x350 kernel/kthread.c:389
 ret_from_fork+0x2e/0x60 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.450 msecs

Crashes (1207):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/08/15 13:02 upstream 91aa6c412d7f 39990d51 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in rfkill_global_led_trigger_worker
2023/07/02 22:16 upstream 995b406c7e97 bfc47836 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2023/07/02 07:08 upstream f8566aa4f176 bfc47836 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2023/06/03 10:19 upstream 4ecd704a4c51 a4ae4f42 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2023/06/03 10:02 upstream 4ecd704a4c51 a4ae4f42 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in rfkill_global_led_trigger_worker
2022/12/21 05:56 upstream b6bb9676f216 d3e76707 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2022/12/20 22:58 upstream 6feb57c2fd7c d3e76707 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2022/11/28 22:06 upstream b7b275e60bcd 247de55b .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in rfkill_global_led_trigger_worker
2022/11/27 15:21 upstream faf68e3523c2 74a66371 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2022/11/27 03:15 upstream 644e9524388a 74a66371 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2022/11/15 12:21 upstream e01d50cbd6ee 97de9cfc .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in rfkill_global_led_trigger_worker
2022/12/02 13:38 upstream 355479c70a48 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in rfkill_global_led_trigger_worker
2022/11/16 12:45 upstream 81e7cfa3a9eb 3a127a31 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in rfkill_global_led_trigger_worker
2024/01/15 07:50 upstream 052d534373b7 551587c1 .config console log report syz C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm32 INFO: task hung in rfkill_global_led_trigger_worker
2024/01/06 17:13 linux-next e2425464bc87 d0304e9c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2023/02/24 01:09 linux-next 0222aa9800b2 9e2ebb3c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2023/06/30 19:58 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e40939bbfc68 01298212 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
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] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/01/13 04:47 linux-next 0a093b2893c7 96166539 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2022/12/26 15:45 linux-next c76083fac3ba 9da18ae8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/19 00:46 upstream 4b377b4868ef c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/18 22:06 upstream 4b377b4868ef c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/18 19:42 upstream 4b377b4868ef c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/18 04:38 upstream 7ee332c9f12b c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/17 05:11 upstream ea5f6ad9ad96 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2024/05/17 02:01 upstream ea5f6ad9ad96 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2024/05/16 19:05 upstream 3c999d1ae3c7 ef5d53ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/16 15:35 upstream 3c999d1ae3c7 ef5d53ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2024/05/16 12:16 upstream 3c999d1ae3c7 ef5d53ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2024/05/16 08:20 upstream 3c999d1ae3c7 ef5d53ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/16 06:22 upstream 3c999d1ae3c7 ef5d53ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/15 10:40 upstream 1b294a1f3561 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/14 08:21 upstream a5131c3fdf26 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/14 06:29 upstream cd97950cbcab fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/14 05:02 upstream cd97950cbcab fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2024/05/14 02:19 upstream cd97950cbcab fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 23:39 upstream cd97950cbcab fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 21:05 upstream cd97950cbcab fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 16:51 upstream a38297e3fb01 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 14:54 upstream a38297e3fb01 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 11:51 upstream a38297e3fb01 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 11:15 upstream a38297e3fb01 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 06:51 upstream ba16c1cf11c9 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2024/05/12 23:56 upstream ba16c1cf11c9 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/12 21:51 upstream ba16c1cf11c9 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/12 19:57 upstream ba16c1cf11c9 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/12 13:43 upstream cf87f46fd34d 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/11 22:34 upstream cf87f46fd34d 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/11 15:54 upstream cf87f46fd34d 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/11 13:46 upstream f4345f05c0df 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/10 20:39 upstream f4345f05c0df f7c35481 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/10 07:42 upstream 448b3fe5a0ea de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in rfkill_global_led_trigger_worker
2024/05/10 03:31 upstream 45db3ab70092 de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/09 17:50 upstream 45db3ab70092 de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2024/05/09 12:24 upstream 45db3ab70092 20bf80e1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/08 19:57 upstream 6d7ddd805123 4cf3f9b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/08 11:03 upstream dccb07f2914c 4cf3f9b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in rfkill_global_led_trigger_worker
2024/05/11 07:00 upstream f4345f05c0df 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in rfkill_global_led_trigger_worker
2024/05/08 17:57 upstream dccb07f2914c 4cf3f9b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in rfkill_global_led_trigger_worker
2023/09/16 08:24 upstream e42bebf6db29 0b6a67ac .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2023/09/04 21:57 upstream 7a1415eebeec db3306a6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-compat INFO: task hung in rfkill_global_led_trigger_worker
2023/07/09 21:19 upstream c192ac735768 668cb1fa .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root INFO: task hung in rfkill_global_led_trigger_worker
2022/11/14 15:19 upstream 094226ad94f4 943f4cb8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in rfkill_global_led_trigger_worker
2024/05/18 17:10 linux-next c75962170e49 c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/15 14:47 linux-next 82d92a9a1b9e fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/14 21:22 linux-next 26dd54d03cd9 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/14 12:51 linux-next 26dd54d03cd9 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 17:54 linux-next 6ba6c795dc73 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/11 05:22 linux-next 75fa778d74b7 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/11 05:20 linux-next 75fa778d74b7 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/11 04:14 linux-next 75fa778d74b7 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in rfkill_global_led_trigger_worker
2024/05/18 18:24 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fda5695d692c c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/05/17 14:18 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fda5695d692c a12e99e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/05/17 11:11 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fda5695d692c c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/05/13 04:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fda5695d692c 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/05/12 14:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fda5695d692c 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/05/10 17:37 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fda5695d692c f7c35481 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
2024/05/09 20:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c4d6737dc9da de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in rfkill_global_led_trigger_worker
* Struck through repros no longer work on HEAD.