------------[ cut here ]------------
======================================================
WARNING: possible circular locking dependency detected
6.0.0-rc7-next-20220929 #1 Not tainted
------------------------------------------------------
syz-executor.1/3878 is trying to acquire lock:
ffffffff853faab8 ((console_sem).lock){....}-{2:2}, at: down_trylock+0xe/0x70
but task is already holding lock:
ffff88803cfaa820 (&ctx->lock){....}-{2:2}, at: __perf_event_task_sched_out+0x53b/0x18d0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #3 (&ctx->lock){....}-{2:2}:
_raw_spin_lock+0x2a/0x40
__perf_event_task_sched_out+0x53b/0x18d0
__schedule+0xedd/0x2470
schedule+0xda/0x1b0
futex_wait_queue+0xf5/0x1e0
futex_wait+0x28e/0x690
do_futex+0x2ff/0x380
__x64_sys_futex+0x1c6/0x4d0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #2 (&rq->__lock){-.-.}-{2:2}:
_raw_spin_lock_nested+0x30/0x40
raw_spin_rq_lock_nested+0x1e/0x30
task_fork_fair+0x63/0x4d0
sched_cgroup_fork+0x3d0/0x540
copy_process+0x4183/0x6e20
kernel_clone+0xe7/0x890
user_mode_thread+0xad/0xf0
rest_init+0x24/0x250
arch_call_rest_init+0xf/0x14
start_kernel+0x4c6/0x4eb
secondary_startup_64_no_verify+0xe0/0xeb
-> #1 (&p->pi_lock){-.-.}-{2:2}:
_raw_spin_lock_irqsave+0x39/0x60
try_to_wake_up+0xab/0x1930
up+0x75/0xb0
__up_console_sem+0x6e/0x80
console_unlock+0x46a/0x590
vprintk_emit+0x1bd/0x560
vprintk+0x84/0xa0
_printk+0xba/0xf1
regdb_fw_cb.cold+0x6c/0xa7
request_firmware_work_func+0x12e/0x240
process_one_work+0xa17/0x16a0
worker_thread+0x637/0x1260
kthread+0x2ed/0x3a0
ret_from_fork+0x22/0x30
-> #0 ((console_sem).lock){....}-{2:2}:
__lock_acquire+0x2a02/0x5e70
lock_acquire+0x1a2/0x530
_raw_spin_lock_irqsave+0x39/0x60
down_trylock+0xe/0x70
__down_trylock_console_sem+0x3b/0xd0
vprintk_emit+0x16b/0x560
vprintk+0x84/0xa0
_printk+0xba/0xf1
report_bug.cold+0x72/0xab
handle_bug+0x3c/0x70
exc_invalid_op+0x14/0x50
asm_exc_invalid_op+0x16/0x20
group_sched_out.part.0+0x2c7/0x460
ctx_sched_out+0x8f1/0xc10
__perf_event_task_sched_out+0x6d0/0x18d0
__schedule+0xedd/0x2470
schedule+0xda/0x1b0
futex_wait_queue+0xf5/0x1e0
futex_wait+0x28e/0x690
do_futex+0x2ff/0x380
__x64_sys_futex+0x1c6/0x4d0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
other info that might help us debug this:
Chain exists of:
(console_sem).lock --> &rq->__lock --> &ctx->lock
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&ctx->lock);
lock(&rq->__lock);
lock(&ctx->lock);
lock((console_sem).lock);
*** DEADLOCK ***
2 locks held by syz-executor.1/3878:
#0: ffff88806ce37e98 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x1cf/0x2470
#1: ffff88803cfaa820 (&ctx->lock){....}-{2:2}, at: __perf_event_task_sched_out+0x53b/0x18d0
stack backtrace:
CPU: 0 PID: 3878 Comm: syz-executor.1 Not tainted 6.0.0-rc7-next-20220929 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Call Trace:
dump_stack_lvl+0x8b/0xb3
check_noncircular+0x263/0x2e0
__lock_acquire+0x2a02/0x5e70
lock_acquire+0x1a2/0x530
_raw_spin_lock_irqsave+0x39/0x60
down_trylock+0xe/0x70
__down_trylock_console_sem+0x3b/0xd0
vprintk_emit+0x16b/0x560
vprintk+0x84/0xa0
_printk+0xba/0xf1
report_bug.cold+0x72/0xab
handle_bug+0x3c/0x70
exc_invalid_op+0x14/0x50
asm_exc_invalid_op+0x16/0x20
RIP: 0010:group_sched_out.part.0+0x2c7/0x460
Code: 5e 41 5f e9 8b ae ef ff e8 86 ae ef ff 65 8b 1d 6b 17 ac 7e 31 ff 89 de e8 26 ab ef ff 85 db 0f 84 8a 00 00 00 e8 69 ae ef ff <0f> 0b e9 a5 fe ff ff e8 5d ae ef ff 48 8d 7d 10 48 b8 00 00 00 00
RSP: 0018:ffff88803e5df8f8 EFLAGS: 00010006
RAX: 0000000040000002 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88803e54d040 RSI: ffffffff81565e67 RDI: 0000000000000005
RBP: ffff8880086605c8 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000001 R12: ffff88803cfaa800
R13: ffff88806ce3d2c0 R14: ffffffff8547c9a0 R15: 0000000000000002
ctx_sched_out+0x8f1/0xc10
__perf_event_task_sched_out+0x6d0/0x18d0
__schedule+0xedd/0x2470
schedule+0xda/0x1b0
futex_wait_queue+0xf5/0x1e0
futex_wait+0x28e/0x690
do_futex+0x2ff/0x380
__x64_sys_futex+0x1c6/0x4d0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fa04500cb19
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:00007fa042582218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fa04511ff68 RCX: 00007fa04500cb19
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fa04511ff68
RBP: 00007fa04511ff60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fa04511ff6c
R13: 00007ffed5ea572f R14: 00007fa042582300 R15: 0000000000022000
netlink: 5280 bytes leftover after parsing attributes in process `syz-executor.1'.
WARNING: CPU: 0 PID: 3878 at kernel/events/core.c:2309 group_sched_out.part.0+0x2c7/0x460
Modules linked in:
CPU: 0 PID: 3878 Comm: syz-executor.1 Not tainted 6.0.0-rc7-next-20220929 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
RIP: 0010:group_sched_out.part.0+0x2c7/0x460
Code: 5e 41 5f e9 8b ae ef ff e8 86 ae ef ff 65 8b 1d 6b 17 ac 7e 31 ff 89 de e8 26 ab ef ff 85 db 0f 84 8a 00 00 00 e8 69 ae ef ff <0f> 0b e9 a5 fe ff ff e8 5d ae ef ff 48 8d 7d 10 48 b8 00 00 00 00
RSP: 0018:ffff88803e5df8f8 EFLAGS: 00010006
RAX: 0000000040000002 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88803e54d040 RSI: ffffffff81565e67 RDI: 0000000000000005
RBP: ffff8880086605c8 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000001 R12: ffff88803cfaa800
R13: ffff88806ce3d2c0 R14: ffffffff8547c9a0 R15: 0000000000000002
FS: 00007fa042582700(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3e9cd25260 CR3: 000000003dcd6000 CR4: 0000000000350ef0
Call Trace:
ctx_sched_out+0x8f1/0xc10
__perf_event_task_sched_out+0x6d0/0x18d0
__schedule+0xedd/0x2470
schedule+0xda/0x1b0
futex_wait_queue+0xf5/0x1e0
futex_wait+0x28e/0x690
do_futex+0x2ff/0x380
__x64_sys_futex+0x1c6/0x4d0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fa04500cb19
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:00007fa042582218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007fa04511ff68 RCX: 00007fa04500cb19
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fa04511ff68
RBP: 00007fa04511ff60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fa04511ff6c
R13: 00007ffed5ea572f R14: 00007fa042582300 R15: 0000000000022000
irq event stamp: 1250
hardirqs last enabled at (1249): [] asm_sysvec_apic_timer_interrupt+0x16/0x20
hardirqs last disabled at (1250): [] __schedule+0x1225/0x2470
softirqs last enabled at (738): [] __irq_exit_rcu+0x11b/0x180
softirqs last disabled at (733): [] __irq_exit_rcu+0x11b/0x180
---[ end trace 0000000000000000 ]---
autofs4:pid:3885:check_dev_ioctl_version: ioctl control interface version mismatch: kernel(1.1), user(2.1), cmd(0xc0189373)
autofs4:pid:3885:validate_dev_ioctl: invalid device control module version supplied for cmd(0xc0189373)
sg_write: data in/out 524252/251 bytes for SCSI command 0x0-- guessing data in;
program syz-executor.1 not setting count and/or reply_len properly
hrtimer: interrupt took 10269 ns
autofs4:pid:3891:check_dev_ioctl_version: ioctl control interface version mismatch: kernel(1.1), user(2.1), cmd(0xc0189373)
autofs4:pid:3891:validate_dev_ioctl: invalid device control module version supplied for cmd(0xc0189373)
loop7: detected capacity change from 0 to 63
loop7: detected capacity change from 0 to 172
loop7: detected capacity change from 0 to 63
loop7: detected capacity change from 0 to 172
I/O error, dev loop7, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Bluetooth: hci2: Opcode 0x c03 failed: -110
Bluetooth: hci2: unexpected cc 0x0c03 length: 249 > 1
Bluetooth: hci2: unexpected cc 0x1003 length: 249 > 9
Bluetooth: hci2: unexpected cc 0x1001 length: 249 > 9
Bluetooth: hci2: unexpected cc 0x0c23 length: 249 > 4
Bluetooth: hci2: unexpected cc 0x0c25 length: 249 > 3
Bluetooth: hci2: unexpected cc 0x0c38 length: 249 > 2
Bluetooth: hci2: HCI_REQ-0x0c1a
Bluetooth: hci2: command 0x0409 tx timeout