syzbot


INFO: task hung in rfkill_sync_work

Status: auto-obsoleted due to no activity on 2023/12/11 11:27
Reported-by: syzbot+dc79cd9dee9686d7f6e7@syzkaller.appspotmail.com
First crash: 172d, last: 172d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in rfkill_sync_work 1 191d 191d 0/3 auto-obsoleted due to no activity on 2023/11/22 22:14
upstream INFO: task hung in rfkill_sync_work net nfc C done 23 2d20h 422d 0/26 upstream: reported C repro on 2022/12/26 19:45

Sample crash report:
INFO: task kworker/0:8:3639 blocked for more than 143 seconds.
      Not tainted 5.15.130-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:8     state:D stack:22144 pid: 3639 ppid:     2 flags:0x00004000
Workqueue: events rfkill_sync_work
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0x12c4/0x4590 kernel/sched/core.c:6372
 schedule+0x11b/0x1f0 kernel/sched/core.c:6455
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6514
 __mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 rfkill_sync_work+0x25/0xe0 net/rfkill/core.c:1028
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
INFO: task kworker/0:15:11432 blocked for more than 143 seconds.
      Not tainted 5.15.130-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:15    state:D stack:27424 pid:11432 ppid:     2 flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0x12c4/0x4590 kernel/sched/core.c:6372
 schedule+0x11b/0x1f0 kernel/sched/core.c:6455
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6514
 __mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
INFO: task syz-executor.1:12496 blocked for more than 143 seconds.
      Not tainted 5.15.130-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:25816 pid:12496 ppid:  3542 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0x12c4/0x4590 kernel/sched/core.c:6372
 schedule+0x11b/0x1f0 kernel/sched/core.c:6455
 schedule_timeout+0xac/0x300 kernel/time/timer.c:1860
 do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
 __flush_work+0x124/0x1a0 kernel/workqueue.c:3094
 __cancel_work_timer+0x519/0x6a0 kernel/workqueue.c:3181
 rfkill_unregister+0x92/0x220 net/rfkill/core.c:1112
 nfc_unregister_device+0x92/0x290 net/nfc/core.c:1167
 virtual_ncidev_close+0x55/0x90 drivers/nfc/virtual_ncidev.c:166
 __fput+0x3bf/0x890 fs/file_table.c:280
 task_work_run+0x129/0x1a0 kernel/task_work.c:164
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
 __syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
 syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
 do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f7b1680b9da
RSP: 002b:00007ffc9e9a0530 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 00007f7b1680b9da
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 00007f7b1692d980 R08: 0000001b30a20000 R09: 000000000000042a
R10: 0000000081a6c62b R11: 0000000000000293 R12: 00000000000a7bc9
R13: ffffffffffffffff R14: 00007f7b16390000 R15: 00000000000a7888
 </TASK>
INFO: task syz-executor.0:12502 blocked for more than 144 seconds.
      Not tainted 5.15.130-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0  state:D stack:24224 pid:12502 ppid:  9076 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0x12c4/0x4590 kernel/sched/core.c:6372
 schedule+0x11b/0x1f0 kernel/sched/core.c:6455
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6514
 __mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 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+0x4c/0x2f0 net/nfc/core.c:179
 rfkill_set_block+0x1e7/0x430 net/rfkill/core.c:345
 rfkill_fop_write+0x5b7/0x790 net/rfkill/core.c:1274
 vfs_write+0x30c/0xe50 fs/read_write.c:592
 ksys_write+0x1a2/0x2c0 fs/read_write.c:647
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7ff6eb032ae9
RSP: 002b:00007ff6e95b40c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ff6eb151f80 RCX: 00007ff6eb032ae9
RDX: 0000000000000008 RSI: 0000000020000240 RDI: 0000000000000003
RBP: 00007ff6eb07e47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007ff6eb151f80 R15: 00007ffcbd806c58
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c91f0e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3259:
 #0: ffff888024af6098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002bb32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
3 locks held by kworker/0:8/3639:
 #0: ffff888011c70d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc9000400fd20 ((work_completion)(&rfkill->sync_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8dc6e648 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_sync_work+0x25/0xe0 net/rfkill/core.c:1028
3 locks held by kworker/0:15/11432:
 #0: ffff888011c70d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc9000a5afd20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
 #2: ffffffff8dc6e648 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
1 lock held by syz-executor.1/12496:
 #0: ffff888020e86190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #0: ffff888020e86190 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x5f/0x290 net/nfc/core.c:1165
2 locks held by syz-executor.0/12502:
 #0: ffffffff8dc6e648 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x1a5/0x790 net/rfkill/core.c:1266
 #1: ffff888020e86190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #1: ffff888020e86190 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
 #1: ffff888020e86190 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x4c/0x2f0 net/nfc/core.c:179
2 locks held by syz-executor.1/12691:
 #0: ffff888073f03518 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
 #1: ffffffff8dc6e648 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.0/12693:
 #0: ffff888026eae118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
 #1: ffffffff8dc6e648 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.1/12695:
 #0: ffff888016f50918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
 #1: ffffffff8dc6e648 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.0/12698:
 #0: ffff888023b62518 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
 #1: ffffffff8dc6e648 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.130-syzkaller #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+0x1e3/0x2cb lib/dump_stack.c:106
 nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
 watchdog+0xe72/0xeb0 kernel/hung_task.c:295
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4736 Comm: kworker/u4:19 Not tainted 5.15.130-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:validate_chain+0x598/0x58b0 kernel/locking/lockdep.c:3794
Code: 5d a0 02 89 c3 e8 48 fd fe ff 85 db 0f 85 2d 04 00 00 48 c7 c0 04 3d e4 8d 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 0b 42 00 00 <83> 3d f5 02 81 0c 00 0f 84 fd 0d 00 00 41 be 01 00 00 00 48 8b 84
RSP: 0018:ffffc900054bf6e0 EFLAGS: 00000046
RAX: 0000000000000000 RBX: 0000000000020029 RCX: 1ffff92000a97efc
RDX: 0000000000000000 RSI: ffff888015de46c0 RDI: ffff888015de3b80
RBP: ffffc900054bf990 R08: dffffc0000000000 R09: fffffbfff1f7b021
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888015de46e0 R14: b6229783707600fa R15: ffff888015de46e0
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff7b099b000 CR3: 0000000022bf1000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
 rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:269
 rcu_read_lock include/linux/rcupdate.h:696 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
 batadv_nc_worker+0xc1/0x5b0 net/batman-adv/network-coding.c:723
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/09/02 11:26 linux-5.15.y 8f790700c974 696ea0d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in rfkill_sync_work
* Struck through repros no longer work on HEAD.