syzbot


INFO: task hung in nfc_rfkill_set_block

Status: upstream: reported C repro on 2023/05/10 12:44
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+911488d8f3df7018e18b@syzkaller.appspotmail.com
First crash: 575d, last: 88d
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2023/07/04 upstream (ToT) d528014517f2 C [report] INFO: task hung in rfkill_global_led_trigger_worker
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in nfc_rfkill_set_block net nfc C done done 280 18h06m 751d 0/28 upstream: reported C repro on 2022/11/15 16:56
linux-5.15 INFO: task hung in nfc_rfkill_set_block origin:upstream C error 14 424d 625d 0/3 upstream: reported C repro on 2023/03/21 08:35
Fix bisection attempts (10)
Created Duration User Patch Repo Result
2024/10/15 01:17 0m bisect fix linux-6.1.y error job log
2024/09/08 06:58 2h57m bisect fix linux-6.1.y OK (0) job log log
2024/05/28 19:08 2h24m bisect fix linux-6.1.y OK (0) job log log
2024/04/21 14:30 2h21m bisect fix linux-6.1.y OK (0) job log log
2024/03/21 02:26 2h16m bisect fix linux-6.1.y OK (0) job log log
2024/02/15 03:57 2h09m bisect fix linux-6.1.y OK (0) job log log
2024/01/06 11:51 2h39m bisect fix linux-6.1.y OK (0) job log log
2023/12/07 08:20 2h02m bisect fix linux-6.1.y OK (0) job log log
2023/11/07 02:23 2h32m bisect fix linux-6.1.y OK (0) job log log
2023/09/15 21:27 2h31m bisect fix linux-6.1.y OK (0) job log log

Sample crash report:
INFO: task kworker/0:0:7 blocked for more than 143 seconds.
      Not tainted 6.1.37-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:0     state:D stack:0     pid:7     ppid:2      flags:0x00000008
Workqueue: events rfkill_op_handler
Call trace:
 __switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0xee4/0x1c98 kernel/sched/core.c:6554
 schedule+0xc4/0x170 kernel/sched/core.c:6630
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6689
 __mutex_lock_common+0xbd8/0x21a0 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
 device_lock include/linux/device.h:836 [inline]
 nfc_dev_down net/nfc/core.c:143 [inline]
 nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179
 rfkill_set_block+0x18c/0x37c net/rfkill/core.c:345
 rfkill_epo+0x8c/0x158 net/rfkill/core.c:454
 __rfkill_handle_global_op net/rfkill/input.c:60 [inline]
 rfkill_op_handler+0x170/0x288 net/rfkill/input.c:108
 process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
 worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
 kthread+0x250/0x2d8 kernel/kthread.c:376
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
INFO: task kworker/0:7:5014 blocked for more than 143 seconds.
      Not tainted 6.1.37-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:7     state:D stack:0     pid:5014  ppid:2      flags:0x00000008
Workqueue: events rfkill_global_led_trigger_worker
Call trace:
 __switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0xee4/0x1c98 kernel/sched/core.c:6554
 schedule+0xc4/0x170 kernel/sched/core.c:6630
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6689
 __mutex_lock_common+0xbd8/0x21a0 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
 rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
 process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
 worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
 kthread+0x250/0x2d8 kernel/kthread.c:376
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
INFO: task syz-executor206:7623 blocked for more than 143 seconds.
      Not tainted 6.1.37-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor206 state:D stack:0     pid:7623  ppid:4271   flags:0x0000000c
Call trace:
 __switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0xee4/0x1c98 kernel/sched/core.c:6554
 schedule+0xc4/0x170 kernel/sched/core.c:6630
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6689
 __mutex_lock_common+0xbd8/0x21a0 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
 rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1130
 nfc_unregister_device+0x98/0x290 net/nfc/core.c:1167
 nci_unregister_device+0x1dc/0x21c net/nfc/nci/core.c:1302
 virtual_ncidev_close+0x70/0xb0 drivers/nfc/virtual_ncidev.c:166
 __fput+0x30c/0x7bc fs/file_table.c:320
 ____fput+0x20/0x30 fs/file_table.c:348
 task_work_run+0x240/0x2f0 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x554/0x1a88 kernel/exit.c:869
 do_group_exit+0x194/0x22c kernel/exit.c:1019
 __do_sys_exit_group kernel/exit.c:1030 [inline]
 __se_sys_exit_group kernel/exit.c:1028 [inline]
 __wake_up_parent+0x0/0x60 kernel/exit.c:1028
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Showing all locks held in the system:
4 locks held by kworker/0:0/7:
 #0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2262
 #1: ffff800019b77c20 ((rfkill_op_work).work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2264
 #2: ffff800017e40628 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_epo+0x58/0x158 net/rfkill/core.c:450
 #3: ffff0000c3234100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
 #3: ffff0000c3234100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
 #3: ffff0000c3234100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179
1 lock held by rcu_tasks_kthre/12:
 #0: ffff8000157a4e70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
 #0: ffff8000157a5670 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
 #0: ffff8000157a4ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3978:
 #0: ffff0000d61e3098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
 #1: ffff80001be602f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
3 locks held by kworker/0:7/5014:
 #0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2262
 #1: ffff80001eb57c20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2264
 #2: ffff800017e40628 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
2 locks held by syz-executor206/7623:
 #0: ffff0000c3234100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:836 [inline]
 #0: ffff0000c3234100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x6c/0x290 net/nfc/core.c:1165
 #1: ffff800017e40628 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1130
1 lock held by syz-executor206/9586:
 #0: ffff8000171735c8 (input_mutex){+.+.}-{3:3}, at: __input_unregister_device+0x2a4/0x5c0 drivers/input/input.c:2219
2 locks held by syz-executor206/9587:
 #0: ffff0000c3caa070 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x16c0 drivers/input/misc/uinput.c:851
 #1: ffff8000171735c8 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x8e4/0xe0c drivers/input/input.c:2389
2 locks held by syz-executor206/9588:
 #0: ffff0000d06fd070 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x16c0 drivers/input/misc/uinput.c:851
 #1: ffff8000171735c8 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x8e4/0xe0c drivers/input/input.c:2389
2 locks held by syz-executor206/9589:
 #0: ffff0000d857d870 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x16c0 drivers/input/misc/uinput.c:851
 #1: ffff8000171735c8 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x8e4/0xe0c drivers/input/input.c:2389
2 locks held by syz-executor206/9590:
 #0: ffff0000e0025870 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x16c0 drivers/input/misc/uinput.c:851
 #1: ffff8000171735c8 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x8e4/0xe0c drivers/input/input.c:2389

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


Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/07/02 03:27 linux-6.1.y 0f4ac6b4c5f0 bfc47836 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2023/07/03 02:04 linux-6.1.y 0f4ac6b4c5f0 bfc47836 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2024/07/20 12:45 linux-6.1.y 9b3f9a5b12dc b88348e9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in nfc_rfkill_set_block
2024/07/06 02:19 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 nfc_rfkill_set_block
2024/08/04 00:26 linux-6.1.y 48d525b0e463 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2024/07/18 16:28 linux-6.1.y 9b3f9a5b12dc 71884c12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2024/04/23 12:51 linux-6.1.y 6741e066ec76 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2024/02/20 02:25 linux-6.1.y 8b4118fabd6e 3af7dd65 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2023/10/05 17:00 linux-6.1.y d23900f974e0 b7d7ff54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2023/06/30 11:21 linux-6.1.y a1c449d00ff8 01298212 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in nfc_rfkill_set_block
2023/05/10 12:44 linux-6.1.y ca48fc16c493 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in nfc_rfkill_set_block
2023/07/01 16:39 linux-6.1.y 0f4ac6b4c5f0 bfc47836 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2023/06/27 03:52 linux-6.1.y e84a4e368abe 4cd5bb25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
* Struck through repros no longer work on HEAD.