syzbot


INFO: task hung in nfc_rfkill_set_block

Status: upstream: reported C repro on 2023/03/21 08:35
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+ec6d9a9ad2419bff5bb4@syzkaller.appspotmail.com
First crash: 574d, last: 373d
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2023/07/09 upstream (ToT) c192ac735768 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 236 7h07m 700d 0/28 upstream: reported C repro on 2022/11/15 16:56
linux-6.1 INFO: task hung in nfc_rfkill_set_block origin:upstream C error 13 37d 524d 0/3 upstream: reported C repro on 2023/05/10 12:44
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/10/07 10:26 13m retest repro linux-5.15.y report log

Sample crash report:
INFO: task kworker/1:1:25 blocked for more than 143 seconds.
      Not tainted 5.15.120-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:1     state:D stack:    0 pid:   25 ppid:     2 flags:0x00000008
Workqueue: events rfkill_op_handler
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e38 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
 __mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
 device_lock include/linux/device.h:760 [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+0x790/0x11b8 kernel/workqueue.c:2307
 worker_thread+0x910/0x1034 kernel/workqueue.c:2454
 kthread+0x37c/0x45c kernel/kthread.c:319
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
INFO: task kworker/1:4:4038 blocked for more than 143 seconds.
      Not tainted 5.15.120-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:4     state:D stack:    0 pid: 4038 ppid:     2 flags:0x00000008
Workqueue: events rfkill_global_led_trigger_worker
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e38 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
 __mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
 rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
 process_one_work+0x790/0x11b8 kernel/workqueue.c:2307
 worker_thread+0x910/0x1034 kernel/workqueue.c:2454
 kthread+0x37c/0x45c kernel/kthread.c:319
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
INFO: task syz-executor142:7825 blocked for more than 143 seconds.
      Not tainted 5.15.120-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor142 state:D stack:    0 pid: 7825 ppid:  3990 flags:0x0000000c
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e38 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
 __mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
 rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1118
 nfc_unregister_device+0x98/0x290 net/nfc/core.c:1167
 nci_unregister_device+0x1e0/0x22c net/nfc/nci/core.c:1306
 virtual_ncidev_close+0x70/0xb0 drivers/nfc/virtual_ncidev.c:166
 __fput+0x30c/0x7f0 fs/file_table.c:280
 ____fput+0x20/0x30 fs/file_table.c:308
 task_work_run+0x130/0x1e4 kernel/task_work.c:164
 exit_task_work include/linux/task_work.h:32 [inline]
 do_exit+0x688/0x2134 kernel/exit.c:872
 do_group_exit+0x110/0x268 kernel/exit.c:994
 __do_sys_exit_group kernel/exit.c:1005 [inline]
 __se_sys_exit_group kernel/exit.c:1003 [inline]
 __wake_up_parent+0x0/0x60 kernel/exit.c:1003
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by kdevtmpfs/23:
 #0: ffff0001b480bd18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:475 [inline]
 #0: ffff0001b480bd18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
 #0: ffff0001b480bd18 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1621 [inline]
 #0: ffff0001b480bd18 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x328/0x1e38 kernel/sched/core.c:6286
4 locks held by kworker/1:1/25:
 #0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2280
 #1: ffff800018a17c00 ((rfkill_op_work).work){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2282
 #2: ffff800016c5ad48 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_epo+0x58/0x158 net/rfkill/core.c:450
 #3: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #3: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
 #3: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179
1 lock held by khungtaskd/27:
 #0: ffff800014ac19a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3723:
 #0: ffff0000d3be0098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
 #1: ffff80001a29b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
3 locks held by kworker/1:4/4038:
 #0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2280
 #1: ffff80001cea7c00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2282
 #2: ffff800016c5ad48 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
2 locks held by syz-executor142/7825:
 #0: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #0: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x6c/0x290 net/nfc/core.c:1165
 #1: ffff800016c5ad48 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1118
1 lock held by syz-executor142/10260:
 #0: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: __input_unregister_device+0x10c/0x304 drivers/input/input.c:2205
1 lock held by syz-executor142/10262:
 #0: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: __input_unregister_device+0x10c/0x304 drivers/input/input.c:2205
2 locks held by syz-executor142/10263:
 #0: ffff0000d2a41870 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x14b0 drivers/input/misc/uinput.c:851
 #1: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x924/0xe4c drivers/input/input.c:2347
2 locks held by syz-executor142/10264:
 #0: ffff0000c5f14070 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x14b0 drivers/input/misc/uinput.c:851
 #1: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x924/0xe4c drivers/input/input.c:2347
2 locks held by syz-executor142/10265:
 #0: ffff0000d5335070 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x14b0 drivers/input/misc/uinput.c:851
 #1: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x924/0xe4c drivers/input/input.c:2347

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


Crashes (14):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/07/09 17:20 linux-5.15.y d54cfc420586 668cb1fa .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2023/10/08 02:06 linux-5.15.y 1edcec18cfb7 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/10/05 20:04 linux-5.15.y b911329317b4 db17ad9f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/09/05 19:39 linux-5.15.y 8f790700c974 0b6286dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/08/18 17:35 linux-5.15.y f6f7927ac664 acb1ba71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/08/08 03:16 linux-5.15.y 38d4ca22a528 b1b6ae3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/07/31 00:07 linux-5.15.y 09996673e313 2a0d0f29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/06/04 11:51 linux-5.15.y 0ab06468cbd1 a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/06/01 04:46 linux-5.15.y 0ab06468cbd1 babc4389 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/05/02 20:06 linux-5.15.y 8a7f2a5c5aa1 52d40fd2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/04/09 23:53 linux-5.15.y d86dfc4d95cd 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/03/21 08:35 linux-5.15.y 8020ae3c051d 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nfc_rfkill_set_block
2023/05/26 12:05 linux-5.15.y 1fe619a7d252 b40ef614 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
2023/04/11 14:36 linux-5.15.y d86dfc4d95cd 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nfc_rfkill_set_block
* Struck through repros no longer work on HEAD.