[v6.1] INFO: task hung in rfkill_unregister

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6741e066ec76 Linux 6.1.87
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16244c2d180000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d37120947ebed5a
dashboard link: https://syzkaller.appspot.com/bug?extid=c07f5c64b3fd1ef07bf0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e09aa9dab3c8/disk-6741e066.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4176a4f5a4d5/vmlinux-6741e066.xz
kernel image: https://storage.googleapis.com/syzbot-assets/970367753980/Image-6741e066.gz.xz

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

INFO: task kworker/u4:3:175 blocked for more than 143 seconds.
Not tainted 6.1.87-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:3 state:D stack:0 pid:175 ppid:2 flags:0x00000008
Workqueue: netns cleanup_net
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
__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
wiphy_unregister+0x1e8/0xa58 net/wireless/core.c:1089
ieee80211_unregister_hw+0x194/0x278 net/mac80211/main.c:1490
mac80211_hwsim_del_radio+0x21c/0x3d8 drivers/net/wireless/mac80211_hwsim.c:4683
hwsim_exit_net+0x518/0x5e0 drivers/net/wireless/mac80211_hwsim.c:5470
ops_exit_list net/core/net_namespace.c:169 [inline]
cleanup_net+0x564/0x994 net/core/net_namespace.c:601
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2292
worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864
INFO: task kworker/0:9:4747 blocked for more than 143 seconds.
Not tainted 6.1.87-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:9 state:D stack:0 pid:4747 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:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
__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:2292
worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864
INFO: task syz-executor.4:6170 blocked for more than 143 seconds.
Not tainted 6.1.87-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:0 pid:6170 ppid:4239 flags:0x0000000d
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
__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:1311
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
get_signal+0x14a0/0x158c kernel/signal.c:2862
do_signal arch/arm64/kernel/signal.c:1076 [inline]
do_notify_resume+0x3ac/0x3474 arch/arm64/kernel/signal.c:1129
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+0x9c/0x168 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-executor.0:6252 blocked for more than 143 seconds.
Not tainted 6.1.87-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:0 pid:6252 ppid:4238 flags:0x0000000d
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
__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:837 [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_fop_write+0x578/0x734 net/rfkill/core.c:1286
vfs_write+0x2a4/0x914 fs/read_write.c:582
ksys_write+0x15c/0x26c 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/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:585
INFO: task syz-executor.2:6280 blocked for more than 143 seconds.
Not tainted 6.1.87-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:0 pid:6280 ppid:5274 flags:0x0000000d
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
__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
hci_unregister_dev+0x308/0x4ac net/bluetooth/hci_core.c:2755
vhci_release+0x7c/0xcc drivers/bluetooth/hci_vhci.c:573
__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
get_signal+0x14a0/0x158c kernel/signal.c:2862
do_signal arch/arm64/kernel/signal.c:1076 [inline]
do_notify_resume+0x314/0x3474 arch/arm64/kernel/signal.c:1129
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+0xb8/0x184 arch/arm64/kernel/entry-common.c:516
el0t_64_sync_handler+0xcc/0xf0 arch/arm64/kernel/entry-common.c:658
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: ffff800015a24e70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffff800015a25670 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffff800015a24ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
4 locks held by kworker/u4:3/175:
#0: ffff0000c0845138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001ddd7c20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff800017e24750 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf4/0x994 net/core/net_namespace.c:563
#3: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1130
2 locks held by getty/3981:
#0: ffff0000d60dd098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bd002f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
1 lock held by syz-executor.4/4239:
#0: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1130
3 locks held by kworker/0:9/4747:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001f1e7c20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
2 locks held by syz-executor.4/6170:
#0: ffff0000d7188100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#0: ffff0000d7188100 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x6c/0x290 net/nfc/core.c:1165
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1130
2 locks held by syz-executor.0/6252:
#0: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x234/0x734 net/rfkill/core.c:1278
#1: ffff0000d7188100 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#1: ffff0000d7188100 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
#1: ffff0000d7188100 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179
1 lock held by syz-executor.2/6280:
#0: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1130
2 locks held by syz-executor.1/6620:
#0: ffff0000f10e4918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.4/6621:
#0: ffff0000f10e1118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.0/6687:
#0: ffff0000dc168118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.2/6721:
#0: ffff0000dca6e118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
1 lock held by syz-executor.3/7122:
#0: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1130
2 locks held by syz-executor.1/7312:
#0: ffff0000d03b0118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.4/7314:
#0: ffff0000cb346918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.0/7316:
#0: ffff0000c376b918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.3/7318:
#0: ffff0000ef98f918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.2/7321:
#0: ffff0000db580118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.1/7329:
#0: ffff0000f1442118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 net/rfkill/core.c:1057
2 locks held by syz-executor.4/7331:
#0: ffff0000f1445918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x44/0x6d0 drivers/bluetooth/hci_vhci.c:378
#1: ffff8000180d0b88 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x44/0x7a4 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