[v6.1] INFO: task hung in rfkill_register

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117ee8b4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link: https://syzkaller.appspot.com/bug?extid=8c4c6f27368bc3043d9d
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c1bd671a9def/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fa0af998ea40/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e5512d873524/Image-f6e38ae6.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8c4c6f...@syzkaller.appspotmail.com

INFO: task syz-executor:4320 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:0 pid:4320 ppid:1 flags:0x00000009
Call trace:
__switch_to+0x2f4/0x568 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0xddc/0x1b18 kernel/sched/core.c:6561
schedule+0xc4/0x170 kernel/sched/core.c:6637
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6696
__mutex_lock_common+0xad4/0x1f38 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
rfkill_register+0x44/0x77c net/rfkill/core.c:1057
wiphy_register+0x1ba8/0x224c net/wireless/core.c:1024
ieee80211_register_hw+0x233c/0x2f68 net/mac80211/main.c:1392
mac80211_hwsim_new_radio+0x2104/0x40dc drivers/net/wireless/mac80211_hwsim.c:4587
hwsim_new_radio_nl+0x878/0xbe0 drivers/net/wireless/mac80211_hwsim.c:5181
genl_family_rcv_msg_doit+0x1f8/0x2f4 net/netlink/genetlink.c:756
genl_family_rcv_msg net/netlink/genetlink.c:833 [inline]
genl_rcv_msg+0x444/0x62c net/netlink/genetlink.c:850
netlink_rcv_skb+0x208/0x3c4 net/netlink/af_netlink.c:2511
genl_rcv+0x38/0x50 net/netlink/genetlink.c:861
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x60c/0x824 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6e8/0x9b0 net/netlink/af_netlink.c:1872
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
__sys_sendto+0x304/0x3fc net/socket.c:2153
__do_sys_sendto net/socket.c:2165 [inline]
__se_sys_sendto net/socket.c:2161 [inline]
__arm64_sys_sendto+0xd8/0xf8 net/socket.c:2161
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 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:585
INFO: task syz-executor:4328 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:0 pid:4328 ppid:1 flags:0x0000000c
Call trace:
__switch_to+0x2f4/0x568 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0xddc/0x1b18 kernel/sched/core.c:6561
schedule+0xc4/0x170 kernel/sched/core.c:6637
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6696
__mutex_lock_common+0xad4/0x1f38 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/0x208 net/rfkill/core.c:1130
hci_unregister_dev+0x314/0x4b4 net/bluetooth/hci_core.c:2722
vhci_release+0x7c/0xcc drivers/bluetooth/hci_vhci.c:573
__fput+0x1bc/0x7c0 fs/file_table.c:320
____fput+0x20/0x30 fs/file_table.c:348
task_work_run+0x1ec/0x270 kernel/task_work.c:203
exit_task_work include/linux/task_work.h:39 [inline]
do_exit+0x54c/0x19a8 kernel/exit.c:880
do_group_exit+0x194/0x22c kernel/exit.c:1022
__do_sys_exit_group kernel/exit.c:1033 [inline]
__se_sys_exit_group kernel/exit.c:1031 [inline]
__wake_up_parent+0x0/0x60 kernel/exit.c:1031
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 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:585
INFO: task kworker/0:3:4372 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:3 state:D stack:0 pid:4372 ppid:2 flags:0x00000008
Workqueue: events rfkill_op_handler
Call trace:
__switch_to+0x2f4/0x568 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0xddc/0x1b18 kernel/sched/core.c:6561
schedule+0xc4/0x170 kernel/sched/core.c:6637
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6696
__mutex_lock_common+0xad4/0x1f38 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:840 [inline]
nfc_dev_down net/nfc/core.c:143 [inline]
nfc_rfkill_set_block+0x4c/0x2a8 net/nfc/core.c:179
rfkill_set_block+0x18c/0x374 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+0x150/0x248 net/rfkill/input.c:108
process_one_work+0x7f4/0x13a8 kernel/workqueue.c:2292
worker_thread+0x8c8/0xfbc kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
INFO: task kworker/0:4:4373 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:4 state:D stack:0 pid:4373 ppid:2 flags:0x00000008
Workqueue: events rfkill_global_led_trigger_worker
Call trace:
__switch_to+0x2f4/0x568 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0xddc/0x1b18 kernel/sched/core.c:6561
schedule+0xc4/0x170 kernel/sched/core.c:6637
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6696
__mutex_lock_common+0xad4/0x1f38 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+0x7f4/0x13a8 kernel/workqueue.c:2292
worker_thread+0x8c8/0xfbc kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
INFO: task syz.0.8:4439 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.8 state:D stack:0 pid:4439 ppid:4323 flags:0x00000009
Call trace:
__switch_to+0x2f4/0x568 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0xddc/0x1b18 kernel/sched/core.c:6561
schedule+0xc4/0x170 kernel/sched/core.c:6637
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6696
__mutex_lock_common+0xad4/0x1f38 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/0x208 net/rfkill/core.c:1130
nfc_unregister_device+0x94/0x288 net/nfc/core.c:1167
nci_unregister_device+0x1dc/0x21c net/nfc/nci/core.c:1311
virtual_ncidev_close+0x70/0xb0 drivers/nfc/virtual_ncidev.c:170
__fput+0x1bc/0x7c0 fs/file_table.c:320
____fput+0x20/0x30 fs/file_table.c:348
task_work_run+0x1ec/0x270 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2038/0x2b28 arch/arm64/kernel/signal.c:1137
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x98/0x138 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
INFO: task syz.1.38:4627 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.38 state:D stack:0 pid:4627 ppid:4319 flags:0x0000000d
Call trace:
__switch_to+0x2f4/0x568 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0xddc/0x1b18 kernel/sched/core.c:6561
schedule+0xc4/0x170 kernel/sched/core.c:6637
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6696
__mutex_lock_common+0xad4/0x1f38 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/0x208 net/rfkill/core.c:1130
hci_unregister_dev+0x314/0x4b4 net/bluetooth/hci_core.c:2722
vhci_release+0x7c/0xcc drivers/bluetooth/hci_vhci.c:573
__fput+0x1bc/0x7c0 fs/file_table.c:320
____fput+0x20/0x30 fs/file_table.c:348
task_work_run+0x1ec/0x270 kernel/task_work.c:203
exit_task_work include/linux/task_work.h:39 [inline]
do_exit+0x54c/0x19a8 kernel/exit.c:880
do_group_exit+0x194/0x22c kernel/exit.c:1022
get_signal+0x11d0/0x1310 kernel/signal.c:2871
do_signal arch/arm64/kernel/signal.c:1081 [inline]
do_notify_resume+0x29c/0x2b28 arch/arm64/kernel/signal.c:1134
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_da+0xb4/0x154 arch/arm64/kernel/entry-common.c:516
el0t_64_sync_handler+0x90/0xf0 arch/arm64/kernel/entry-common.c:658
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
INFO: task syz.3.72:4745 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.72 state:D stack:0 pid:4745 ppid:4332 flags:0x00000001
Call trace:
__switch_to+0x2f4/0x568 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0xddc/0x1b18 kernel/sched/core.c:6561
schedule+0xc4/0x170 kernel/sched/core.c:6637
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6696
__mutex_lock_common+0xad4/0x1f38 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
genl_lock net/netlink/genetlink.c:33 [inline]
genl_rcv_msg+0xec/0x62c net/netlink/genetlink.c:848
netlink_rcv_skb+0x208/0x3c4 net/netlink/af_netlink.c:2511
genl_rcv+0x38/0x50 net/netlink/genetlink.c:861
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x60c/0x824 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6e8/0x9b0 net/netlink/af_netlink.c:1872
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
__sys_sendto+0x304/0x3fc net/socket.c:2153
__do_sys_sendto net/socket.c:2165 [inline]
__se_sys_sendto net/socket.c:2161 [inline]
__arm64_sys_sendto+0xd8/0xf8 net/socket.c:2161
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 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:585
INFO: task syz-executor:4752 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:0 pid:4752 ppid:1 flags:0x00000000
Call trace:
__switch_to+0x2f4/0x568 arch/arm64/kernel/process.c:555
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0xddc/0x1b18 kernel/sched/core.c:6561
schedule+0xc4/0x170 kernel/sched/core.c:6637
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6696
__mutex_lock_common+0xad4/0x1f38 kernel/locking/mutex.c:679
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
rfkill_register+0x44/0x77c net/rfkill/core.c:1057
hci_register_dev+0x3e4/0x95c net/bluetooth/hci_core.c:2622
__vhci_create_device drivers/bluetooth/hci_vhci.c:340 [inline]
vhci_create_device+0x350/0x6cc drivers/bluetooth/hci_vhci.c:379
vhci_get_user drivers/bluetooth/hci_vhci.c:436 [inline]
vhci_write+0x30c/0x3ac drivers/bluetooth/hci_vhci.c:516
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x5ac/0x7c4 fs/read_write.c:584
ksys_write+0x120/0x210 fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 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:585

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015297870 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x40/0xbb4 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffff800015298090 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x40/0xbb4 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffff800015296f00 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by getty/4078:
#0: ffff0000d63c4098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff8000207be2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x2ec/0xf9c drivers/tty/n_tty.c:2198
3 locks held by syz-executor/4320:
#0: ffff80001778cd70 (cb_lock){++++}-{3:3}, at: genl_rcv+0x28/0x50 net/netlink/genetlink.c:860
#1: ffff80001778cb88 (genl_mutex){+.+.}-{3:3}, at: genl_lock net/netlink/genetlink.c:33 [inline]
#1: ffff80001778cb88 (genl_mutex){+.+.}-{3:3}, at: genl_rcv_msg+0xec/0x62c net/netlink/genetlink.c:848
#2: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
1 lock held by syz-executor/4328:
#0: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x208 net/rfkill/core.c:1130
4 locks held by kworker/0:3/4372:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x6b4/0x13a8 kernel/workqueue.c:2265
#1: ffff8000210c7c20 ((rfkill_op_work).work){+.+.}-{0:0}, at: process_one_work+0x6f8/0x13a8 kernel/workqueue.c:2267
#2: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_epo+0x58/0x158 net/rfkill/core.c:450
#3: ffff0000cce5d100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:840 [inline]
#3: ffff0000cce5d100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
#3: ffff0000cce5d100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x4c/0x2a8 net/nfc/core.c:179
3 locks held by kworker/0:4/4373:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x6b4/0x13a8 kernel/workqueue.c:2265
#1: ffff8000210d7c20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x6f8/0x13a8 kernel/workqueue.c:2267
#2: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
2 locks held by syz.0.8/4439:
#0: ffff0000cce5d100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:840 [inline]
#0: ffff0000cce5d100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x68/0x288 net/nfc/core.c:1165
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x208 net/rfkill/core.c:1130
1 lock held by syz.1.38/4627:
#0: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x208 net/rfkill/core.c:1130
2 locks held by syz.3.72/4745:
#0: ffff80001778cd70 (cb_lock){++++}-{3:3}, at: genl_rcv+0x28/0x50 net/netlink/genetlink.c:860
#1: ffff80001778cb88 (genl_mutex){+.+.}-{3:3}, at: genl_lock net/netlink/genetlink.c:33 [inline]
#1: ffff80001778cb88 (genl_mutex){+.+.}-{3:3}, at: genl_rcv_msg+0xec/0x62c net/netlink/genetlink.c:848
2 locks held by syz-executor/4752:
#0: ffff0000d5068118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4755:
#0: ffff0000dbfe3118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4757:
#0: ffff0000dbfe0118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4759:
#0: ffff0000f4174118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4773:
#0: ffff0000f5c49118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4778:
#0: ffff0000d3149118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4782:
#0: ffff0000dbaad918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4784:
#0: ffff0000dbaac118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4786:
#0: ffff0000d41b6918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4792:
#0: ffff0000dd729118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4795:
#0: ffff0000d506d918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4799:
#0: ffff0000c369c918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4801:
#0: ffff0000c369f118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057
2 locks held by syz-executor/4803:
#0: ffff0000df689918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x3c/0x6cc drivers/bluetooth/hci_vhci.c:378
#1: ffff8000179df8e8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x77c net/rfkill/core.c:1057

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



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup