name failslab, interval 1, probability 0, space 0, times 0 CPU: 1 PID: 31758 Comm: syz-executor.5 Not tainted 5.10.228 #1 ====================================================== Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: WARNING: possible circular locking dependency detected __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x107/0x167 lib/dump_stack.c:118 5.10.228 #1 Not tainted fail_dump lib/fault-inject.c:52 [inline] should_fail.cold+0x5/0xa lib/fault-inject.c:146 ------------------------------------------------------ syz-executor.2/31754 is trying to acquire lock: ffff88800da68b78 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 (work_completion)(&hdev->bg_scan_update) mem_pool_alloc mm/kmemleak.c:423 [inline] create_object.isra.0+0x3a/0xa20 mm/kmemleak.c:578 ){+.+.}-{0:0} , at: __flush_work+0xdd/0xa90 kernel/workqueue.c:3050 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] __kmalloc+0x16e/0x390 mm/slub.c:3967 but task is already holding lock: kmalloc include/linux/slab.h:557 [inline] p9_fcall_init+0x97/0x290 net/9p/client.c:232 ffffffff8561e288 p9_tag_alloc net/9p/client.c:281 [inline] p9_client_prepare_req.part.0+0xf4/0xac0 net/9p/client.c:706 (rfkill_global_mutex p9_client_prepare_req net/9p/client.c:811 [inline] p9_client_rpc+0x220/0x1370 net/9p/client.c:743 ){+.+.}-{3:3}, 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}: __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 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 p9_client_version net/9p/client.c:957 [inline] p9_client_create+0xa76/0x11c0 net/9p/client.c:1057 ){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:968 [inline] __mutex_lock+0x13d/0x10b0 kernel/locking/mutex.c:1109 vhci_send_frame+0x63/0xa0 drivers/bluetooth/hci_vhci.c:71 hci_send_frame+0x1b9/0x320 net/bluetooth/hci_core.c:4065 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 process_one_work+0x9a9/0x14b0 kernel/workqueue.c:2282 worker_thread+0x61d/0x1310 kernel/workqueue.c:2428 kthread+0x38f/0x470 kernel/kthread.c:328 v9fs_session_init+0x1dd/0x1680 fs/9p/v9fs.c:406 ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:298 -> #2 ( (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 v9fs_mount+0x79/0x8f0 fs/9p/vfs_super.c:126 do_group_exit+0x125/0x310 kernel/exit.c:982 get_signal+0x4bc/0x2350 kernel/signal.c:2762 arch_do_signal_or_restart+0x2b7/0x1990 arch/x86/kernel/signal.c:805 handle_signal_work kernel/entry/common.c:145 [inline] exit_to_user_mode_loop kernel/entry/common.c:169 [inline] exit_to_user_mode_prepare+0x10f/0x190 kernel/entry/common.c:199 legacy_get_tree+0x105/0x220 fs/fs_context.c:593 syscall_exit_to_user_mode+0x38/0x1d0 kernel/entry/common.c:274 ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:291 vfs_get_tree+0x8e/0x300 fs/super.c:1572 -> #1 ( do_new_mount fs/namespace.c:2917 [inline] path_mount+0x1429/0x2120 fs/namespace.c:3247 &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 do_mount fs/namespace.c:3260 [inline] __do_sys_mount fs/namespace.c:3468 [inline] __se_sys_mount fs/namespace.c:3445 [inline] __x64_sys_mount+0x282/0x300 fs/namespace.c:3445 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 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 __flush_work+0x105/0xa90 kernel/workqueue.c:3053 __cancel_work_timer+0x368/0x4c0 kernel/workqueue.c:3144 entry_SYSCALL_64_after_hwframe+0x67/0xd1 hci_request_cancel_all+0x73/0x230 net/bluetooth/hci_request.c:3440 RIP: 0033:0x7fa6f1644b19 hci_dev_do_close+0xd9/0x1240 net/bluetooth/hci_core.c:1733 hci_rfkill_set_block+0x166/0x1a0 net/bluetooth/hci_core.c:2223 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 rfkill_set_block+0x1fd/0x540 net/rfkill/core.c:341 rfkill_fop_write+0x253/0x4b0 net/rfkill/core.c:1240 RSP: 002b:00007fa6eebba188 EFLAGS: 00000246 vfs_write+0x29a/0xb10 fs/read_write.c:603 ORIG_RAX: 00000000000000a5 ksys_write+0x1f6/0x260 fs/read_write.c:658 RAX: ffffffffffffffda RBX: 00007fa6f1757f60 RCX: 00007fa6f1644b19 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x67/0xd1 RDX: 00000000200000c0 RSI: 0000000020000040 RDI: 0000000000000000 RBP: 00007fa6eebba1d0 R08: 0000000020000140 R09: 0000000000000000 other info that might help us debug this: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002 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.2/31754: #0: R13: 00007ffcdd2a157f R14: 00007fa6eebba300 R15: 0000000000022000 ffffffff8561e288 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0xff/0x4b0 net/rfkill/core.c:1232 stack backtrace: netlink: 20 bytes leftover after parsing attributes in process `syz-executor.7'. CPU: 0 PID: 31754 Comm: syz-executor.2 Not tainted 5.10.228 #1 EXT4-fs (sda): re-mounted. Opts: journal_ioprio=0x0000000000000000,,errors=continue 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 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:0x7f8da4c3bb19 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:00007f8da21b1188 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f8da4d4ef60 RCX: 00007f8da4c3bb19 RDX: 0000000000000008 RSI: 0000000020000080 RDI: 0000000000000003 RBP: 00007f8da4c95f6d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe65dd851f R14: 00007f8da21b1300 R15: 0000000000022000 hpet: Lost 10 RTC interrupts netlink: 20 bytes leftover after parsing attributes in process `syz-executor.7'. netlink: 20 bytes leftover after parsing attributes in process `syz-executor.7'. EXT4-fs (sda): re-mounted. Opts: journal_ioprio=0x0000000000000000,,errors=continue EXT4-fs (sda): re-mounted. Opts: journal_ioprio=0x0000000000000000,,errors=continue hpet: Lost 1 RTC interrupts ---------------- 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