genl_family_rcv_msg net/netlink/genetlink.c:783 [inline] genl_rcv_msg+0x36a/0x5a0 net/netlink/genetlink.c:800 ====================================================== WARNING: possible circular locking dependency detected 5.10.237 #1 Not tainted netlink_rcv_skb+0x14b/0x430 net/netlink/af_netlink.c:2485 ------------------------------------------------------ syz-executor.6/10656 is trying to acquire lock: ffff888014944b78 ( (work_completion)(&hdev->bg_scan_update) genl_rcv+0x24/0x40 net/netlink/genetlink.c:811 ){+.+.}-{0:0} netlink_unicast_kernel net/netlink/af_netlink.c:1307 [inline] netlink_unicast+0x54e/0x800 net/netlink/af_netlink.c:1333 , at: __flush_work+0xdd/0xa90 kernel/workqueue.c:3050 but task is already holding lock: netlink_sendmsg+0x90f/0xe00 net/netlink/af_netlink.c:1901 ffffffff8561f228 ( rfkill_global_mutex sock_sendmsg_nosec net/socket.c:651 [inline] __sock_sendmsg+0x154/0x190 net/socket.c:663 ){+.+.}-{3:3} ____sys_sendmsg+0x70d/0x870 net/socket.c:2378 , at: rfkill_fop_write+0xff/0x4b0 net/rfkill/core.c:1232 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #4 ( rfkill_global_mutex ){+.+.}-{3:3} ___sys_sendmsg+0xf3/0x170 net/socket.c:2432 : __mutex_lock_common kernel/locking/mutex.c:968 [inline] __mutex_lock+0x13d/0x10b0 kernel/locking/mutex.c:1109 rfkill_register+0x36/0xa10 net/rfkill/core.c:1016 hci_register_dev+0x42e/0xc00 net/bluetooth/hci_core.c:3774 __vhci_create_device+0x2c8/0x5c0 drivers/bluetooth/hci_vhci.c:129 vhci_create_device drivers/bluetooth/hci_vhci.c:153 [inline] vhci_open_timeout+0x38/0x50 drivers/bluetooth/hci_vhci.c:310 process_one_work+0x9a9/0x14b0 kernel/workqueue.c:2282 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2461 worker_thread+0x61d/0x1310 kernel/workqueue.c:2428 kthread+0x38f/0x470 kernel/kthread.c:328 ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:298 -> #3 ( &data->open_mutex do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 ){+.+.}-{3:3} entry_SYSCALL_64_after_hwframe+0x67/0xd1 : RIP: 0033:0x7f6903ae8b19 __mutex_lock_common kernel/locking/mutex.c:968 [inline] __mutex_lock+0x13d/0x10b0 kernel/locking/mutex.c:1109 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 vhci_send_frame+0x63/0xa0 drivers/bluetooth/hci_vhci.c:71 RSP: 002b:00007f690105e188 EFLAGS: 00000246 hci_send_frame+0x1b9/0x320 net/bluetooth/hci_core.c:4065 ORIG_RAX: 000000000000002e hci_sched_acl_pkt net/bluetooth/hci_core.c:4590 [inline] hci_sched_acl net/bluetooth/hci_core.c:4675 [inline] hci_tx_work+0xfb4/0x15d0 net/bluetooth/hci_core.c:4741 RAX: ffffffffffffffda RBX: 00007f6903bfbf60 RCX: 00007f6903ae8b19 process_one_work+0x9a9/0x14b0 kernel/workqueue.c:2282 RDX: 0000000000000000 RSI: 00000000200002c0 RDI: 0000000000000004 worker_thread+0x61d/0x1310 kernel/workqueue.c:2428 RBP: 00007f690105e1d0 R08: 0000000000000000 R09: 0000000000000000 kthread+0x38f/0x470 kernel/kthread.c:328 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002 ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:298 R13: 00007ffcd37e374f R14: 00007f690105e300 R15: 0000000000022000 -> #2 hpet: Lost 7 RTC interrupts ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}: __flush_work+0x105/0xa90 kernel/workqueue.c:3053 hci_dev_do_close+0x131/0x1240 net/bluetooth/hci_core.c:1745 hci_unregister_dev+0x179/0x460 net/bluetooth/hci_core.c:3854 vhci_release+0x70/0xf0 drivers/bluetooth/hci_vhci.c:345 __fput+0x285/0x9f0 fs/file_table.c:281 task_work_run+0xe2/0x1a0 kernel/task_work.c:185 exit_task_work include/linux/task_work.h:33 [inline] do_exit+0xb6f/0x2600 kernel/exit.c:860 do_group_exit+0x125/0x310 kernel/exit.c:982 __do_sys_exit_group kernel/exit.c:993 [inline] __se_sys_exit_group kernel/exit.c:991 [inline] __x64_sys_exit_group+0x3a/0x50 kernel/exit.c:991 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 netlink: 4 bytes leftover after parsing attributes in process `syz-executor.2'. entry_SYSCALL_64_after_hwframe+0x67/0xd1 -> #1 (&hdev->req_lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:968 [inline] __mutex_lock+0x13d/0x10b0 kernel/locking/mutex.c:1109 hci_req_sync net/bluetooth/hci_request.c:277 [inline] bg_scan_update+0x82/0x500 net/bluetooth/hci_request.c:2897 process_one_work+0x9a9/0x14b0 kernel/workqueue.c:2282 worker_thread+0x61d/0x1310 kernel/workqueue.c:2428 kthread+0x38f/0x470 kernel/kthread.c:328 ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:298 -> #0 ((work_completion)(&hdev->bg_scan_update)){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:2988 [inline] check_prevs_add kernel/locking/lockdep.c:3113 [inline] validate_chain kernel/locking/lockdep.c:3729 [inline] __lock_acquire+0x29e7/0x5b00 kernel/locking/lockdep.c:4955 lock_acquire kernel/locking/lockdep.c:5566 [inline] lock_acquire+0x197/0x470 kernel/locking/lockdep.c:5531 __flush_work+0x105/0xa90 kernel/workqueue.c:3053 __cancel_work_timer+0x368/0x4c0 kernel/workqueue.c:3144 hci_request_cancel_all+0x73/0x230 net/bluetooth/hci_request.c:3440 hci_dev_do_close+0xd9/0x1240 net/bluetooth/hci_core.c:1733 hci_rfkill_set_block+0x166/0x1a0 net/bluetooth/hci_core.c:2223 rfkill_set_block+0x1fd/0x540 net/rfkill/core.c:341 rfkill_fop_write+0x253/0x4b0 net/rfkill/core.c:1240 vfs_write+0x29a/0xb10 fs/read_write.c:603 ksys_write+0x1f6/0x260 fs/read_write.c:658 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x67/0xd1 other info that might help us debug this: Chain exists of: (work_completion)(&hdev->bg_scan_update) --> &data->open_mutex --> rfkill_global_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(rfkill_global_mutex); lock(&data->open_mutex); lock(rfkill_global_mutex); lock((work_completion)(&hdev->bg_scan_update)); *** DEADLOCK *** 1 lock held by syz-executor.6/10656: #0: ffffffff8561f228 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0xff/0x4b0 net/rfkill/core.c:1232 stack backtrace: CPU: 1 PID: 10656 Comm: syz-executor.6 Not tainted 5.10.237 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x107/0x167 lib/dump_stack.c:118 check_noncircular+0x263/0x2e0 kernel/locking/lockdep.c:2123 check_prev_add kernel/locking/lockdep.c:2988 [inline] check_prevs_add kernel/locking/lockdep.c:3113 [inline] validate_chain kernel/locking/lockdep.c:3729 [inline] __lock_acquire+0x29e7/0x5b00 kernel/locking/lockdep.c:4955 lock_acquire kernel/locking/lockdep.c:5566 [inline] lock_acquire+0x197/0x470 kernel/locking/lockdep.c:5531 __flush_work+0x105/0xa90 kernel/workqueue.c:3053 __cancel_work_timer+0x368/0x4c0 kernel/workqueue.c:3144 platform regulatory.0: loading /lib/firmware/updates/regulatory.db failed with error -12 platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 hci_request_cancel_all+0x73/0x230 net/bluetooth/hci_request.c:3440 hci_dev_do_close+0xd9/0x1240 net/bluetooth/hci_core.c:1733 hci_rfkill_set_block+0x166/0x1a0 net/bluetooth/hci_core.c:2223 rfkill_set_block+0x1fd/0x540 net/rfkill/core.c:341 rfkill_fop_write+0x253/0x4b0 net/rfkill/core.c:1240 vfs_write+0x29a/0xb10 fs/read_write.c:603 ksys_write+0x1f6/0x260 fs/read_write.c:658 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x67/0xd1 RIP: 0033:0x7f2743570b19 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f2740ae6188 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f2743683f60 RCX: 00007f2743570b19 RDX: 0000000000000008 RSI: 0000000020000080 RDI: 0000000000000003 RBP: 00007f27435caf6d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe6352b02f R14: 00007f2740ae6300 R15: 0000000000022000 wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50 wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50 IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready netlink: 4 bytes leftover after parsing attributes in process `syz-executor.2'. FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 CPU: 0 PID: 10677 Comm: syz-executor.7 Not tainted 5.10.237 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x107/0x167 lib/dump_stack.c:118 fail_dump lib/fault-inject.c:52 [inline] should_fail.cold+0x5/0xa lib/fault-inject.c:146 should_failslab+0x5/0x20 mm/slab_common.c:1200 slab_pre_alloc_hook mm/slab.h:515 [inline] slab_alloc_node mm/slub.c:2821 [inline] slab_alloc mm/slub.c:2904 [inline] kmem_cache_alloc+0x5b/0x310 mm/slub.c:2909 mem_pool_alloc mm/kmemleak.c:423 [inline] create_object.isra.0+0x3a/0xa20 mm/kmemleak.c:578 kmemleak_alloc_recursive include/linux/kmemleak.h:43 [inline] slab_post_alloc_hook mm/slab.h:534 [inline] slab_alloc_node mm/slub.c:2896 [inline] slab_alloc mm/slub.c:2904 [inline] kmem_cache_alloc+0x159/0x310 mm/slub.c:2909 kmem_cache_zalloc include/linux/slab.h:654 [inline] lsm_file_alloc security/security.c:571 [inline] security_file_alloc+0x34/0x170 security/security.c:1472 __alloc_file+0xb7/0x320 fs/file_table.c:106 alloc_empty_file+0x6d/0x170 fs/file_table.c:151 path_openat+0xe6/0x2770 fs/namei.c:3411 do_file_open_root+0x268/0x4e0 fs/namei.c:3480 file_open_root+0x2b8/0x440 fs/open.c:1207 kernel_read_file_from_path_initns+0x178/0x250 fs/kernel_read_file.c:163 fw_get_filesystem_firmware drivers/base/firmware_loader/main.c:534 [inline] _request_firmware+0xc80/0x13a0 drivers/base/firmware_loader/main.c:854 request_firmware+0x32/0x50 drivers/base/firmware_loader/main.c:923 reg_reload_regdb+0x7a/0x240 net/wireless/reg.c:1094 genl_family_rcv_msg_doit+0x22d/0x330 net/netlink/genetlink.c:739 genl_family_rcv_msg net/netlink/genetlink.c:783 [inline] genl_rcv_msg+0x36a/0x5a0 net/netlink/genetlink.c:800 netlink_rcv_skb+0x14b/0x430 net/netlink/af_netlink.c:2485 genl_rcv+0x24/0x40 net/netlink/genetlink.c:811 netlink_unicast_kernel net/netlink/af_netlink.c:1307 [inline] netlink_unicast+0x54e/0x800 net/netlink/af_netlink.c:1333 netlink_sendmsg+0x90f/0xe00 net/netlink/af_netlink.c:1901 sock_sendmsg_nosec net/socket.c:651 [inline] __sock_sendmsg+0x154/0x190 net/socket.c:663 ____sys_sendmsg+0x70d/0x870 net/socket.c:2378 ___sys_sendmsg+0xf3/0x170 net/socket.c:2432 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2461 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x67/0xd1 RIP: 0033:0x7f6903ae8b19 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f690105e188 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6903bfbf60 RCX: 00007f6903ae8b19 RDX: 0000000000000000 RSI: 00000000200002c0 RDI: 0000000000000004 RBP: 00007f690105e1d0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002 R13: 00007ffcd37e374f R14: 00007f690105e300 R15: 0000000000022000 hpet: Lost 5 RTC interrupts platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 ---------------- Code disassembly (best guess), 1 bytes skipped: 0: ff c3 inc %ebx 2: 66 2e 0f 1f 84 00 00 nopw %cs:0x0(%rax,%rax,1) 9: 00 00 00 c: 0f 1f 40 00 nopl 0x0(%rax) 10: 48 89 f8 mov %rdi,%rax 13: 48 89 f7 mov %rsi,%rdi 16: 48 89 d6 mov %rdx,%rsi 19: 48 89 ca mov %rcx,%rdx 1c: 4d 89 c2 mov %r8,%r10 1f: 4d 89 c8 mov %r9,%r8 22: 4c 8b 4c 24 08 mov 0x8(%rsp),%r9 27: 0f 05 syscall * 29: 48 3d 01 f0 ff ff cmp $0xfffffffffffff001,%rax <-- trapping instruction 2f: 73 01 jae 0x32 31: c3 retq 32: 48 c7 c1 bc ff ff ff mov $0xffffffffffffffbc,%rcx 39: f7 d8 neg %eax 3b: 64 89 01 mov %eax,%fs:(%rcx) 3e: 48 rex.W