------------[ cut here ]------------
======================================================
WARNING: possible circular locking dependency detected
6.0.0-rc7-next-20220930 #1 Not tainted
------------------------------------------------------
syz-executor.1/3812 is trying to acquire lock:
ffffffff853faab8 ((console_sem).lock){....}-{2:2}, at: down_trylock+0xe/0x70
but task is already holding lock:
ffff88800dd14420 (&ctx->lock){....}-{2:2}, at: __perf_event_task_sched_in+0x2a0/0x6e0
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
exit_to_user_mode_prepare+0x114/0x1a0
syscall_exit_to_user_mode+0x19/0x40
do_syscall_64+0x48/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
kauditd_hold_skb.cold+0x3f/0x4e
kauditd_send_queue+0x233/0x290
kauditd_thread+0x5f9/0x9c0
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
event_filter_match+0x422/0x660
merge_sched_in+0x107/0x1110
visit_groups_merge.constprop.0.isra.0+0x4fc/0xef0
ctx_sched_in+0x2e6/0x770
perf_event_sched_in+0x58/0x80
__perf_event_task_sched_in+0x408/0x6e0
finish_task_switch.isra.0+0x46d/0x8a0
__schedule+0x89b/0x2470
preempt_schedule_common+0x45/0xc0
__cond_resched+0x17/0x30
__sys_sendmmsg+0x226/0x460
__x64_sys_sendmmsg+0x99/0x100
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/3812:
#0: ffff88806ce3d2e0 (&cpuctx_lock){....}-{2:2}, at: __perf_event_task_sched_in+0x28f/0x6e0
#1: ffff88800dd14420 (&ctx->lock){....}-{2:2}, at: __perf_event_task_sched_in+0x2a0/0x6e0
stack backtrace:
CPU: 0 PID: 3812 Comm: syz-executor.1 Not tainted 6.0.0-rc7-next-20220930 #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:event_filter_match+0x422/0x660
Code: 00 00 00 e9 7c fc ff ff e8 7b 33 f1 ff 65 8b 2d 00 9d ad 7e 31 ff 89 ee e8 1b 30 f1 ff 85 ed 0f 84 ef 00 00 00 e8 5e 33 f1 ff <0f> 0b eb 9f e8 d5 a1 23 00 e9 17 fc ff ff e8 4b 33 f1 ff 48 8d 7b
RSP: 0018:ffff88801811f828 EFLAGS: 00010006
RAX: 0000000040000002 RBX: ffff888034ac8000 RCX: 0000000000000000
RDX: ffff8880177d3580 RSI: ffffffff8154d8d2 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: ffffffff865b401b R12: ffff888034ac8220
R13: 0000000000000000 R14: ffff888034ac80a8 R15: ffff888034ac8220
merge_sched_in+0x107/0x1110
visit_groups_merge.constprop.0.isra.0+0x4fc/0xef0
ctx_sched_in+0x2e6/0x770
perf_event_sched_in+0x58/0x80
__perf_event_task_sched_in+0x408/0x6e0
finish_task_switch.isra.0+0x46d/0x8a0
__schedule+0x89b/0x2470
preempt_schedule_common+0x45/0xc0
__cond_resched+0x17/0x30
__sys_sendmmsg+0x226/0x460
__x64_sys_sendmmsg+0x99/0x100
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fb0ac9d0b19
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:00007fb0a9f46188 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00007fb0acae3f60 RCX: 00007fb0ac9d0b19
RDX: 0000000004000101 RSI: 0000000020002880 RDI: 0000000000000006
RBP: 00007fb0aca2af6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000015b74 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdd6b8780f R14: 00007fb0a9f46300 R15: 0000000000022000
WARNING: CPU: 0 PID: 3812 at kernel/events/core.c:2233 event_filter_match+0x422/0x660
Modules linked in:
CPU: 0 PID: 3812 Comm: syz-executor.1 Not tainted 6.0.0-rc7-next-20220930 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
RIP: 0010:event_filter_match+0x422/0x660
Code: 00 00 00 e9 7c fc ff ff e8 7b 33 f1 ff 65 8b 2d 00 9d ad 7e 31 ff 89 ee e8 1b 30 f1 ff 85 ed 0f 84 ef 00 00 00 e8 5e 33 f1 ff <0f> 0b eb 9f e8 d5 a1 23 00 e9 17 fc ff ff e8 4b 33 f1 ff 48 8d 7b
RSP: 0018:ffff88801811f828 EFLAGS: 00010006
RAX: 0000000040000002 RBX: ffff888034ac8000 RCX: 0000000000000000
RDX: ffff8880177d3580 RSI: ffffffff8154d8d2 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: ffffffff865b401b R12: ffff888034ac8220
R13: 0000000000000000 R14: ffff888034ac80a8 R15: ffff888034ac8220
FS: 00007fb0a9f46700(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007faaf085f6f4 CR3: 00000000328e2000 CR4: 0000000000350ef0
Call Trace:
merge_sched_in+0x107/0x1110
visit_groups_merge.constprop.0.isra.0+0x4fc/0xef0
ctx_sched_in+0x2e6/0x770
perf_event_sched_in+0x58/0x80
__perf_event_task_sched_in+0x408/0x6e0
finish_task_switch.isra.0+0x46d/0x8a0
__schedule+0x89b/0x2470
preempt_schedule_common+0x45/0xc0
__cond_resched+0x17/0x30
__sys_sendmmsg+0x226/0x460
__x64_sys_sendmmsg+0x99/0x100
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fb0ac9d0b19
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:00007fb0a9f46188 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00007fb0acae3f60 RCX: 00007fb0ac9d0b19
RDX: 0000000004000101 RSI: 0000000020002880 RDI: 0000000000000006
RBP: 00007fb0aca2af6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000015b74 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdd6b8780f R14: 00007fb0a9f46300 R15: 0000000000022000
irq event stamp: 23762
hardirqs last enabled at (23761): [] call_rcu+0x589/0xa30
hardirqs last disabled at (23762): [] __schedule+0x1225/0x2470
softirqs last enabled at (23758): [] ipv4_confirm_neigh+0x42d/0x10d0
softirqs last disabled at (23756): [] ipv4_confirm_neigh+0x123/0x10d0
---[ end trace 0000000000000000 ]---
loop6: detected capacity change from 0 to 256
FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop6: detected capacity change from 0 to 256
FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop0: detected capacity change from 0 to 16368
nfs: Unknown parameter 'jfs'
loop0: detected capacity change from 0 to 16368
nfs: Unknown parameter 'jfs'
loop6: detected capacity change from 0 to 256
loop4: detected capacity change from 0 to 264192
=======================================================
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
nfs4: Unknown parameter '/dev/input/mouse#'
FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop4: detected capacity change from 0 to 264192
nfs4: Unknown parameter '/dev/input/mouse#'
nfs: Unknown parameter '@{{%{/-'
Bluetooth: hci5: Opcode 0x c03 failed: -110
Bluetooth: hci5: unexpected cc 0x0c03 length: 249 > 1
Bluetooth: hci5: unexpected cc 0x1003 length: 249 > 9
Bluetooth: hci5: unexpected cc 0x1001 length: 249 > 9
Bluetooth: hci5: unexpected cc 0x0c23 length: 249 > 4
Bluetooth: hci5: unexpected cc 0x0c25 length: 249 > 3
Bluetooth: hci5: unexpected cc 0x0c38 length: 249 > 2
Bluetooth: hci5: HCI_REQ-0x0c1a
Bluetooth: hci5: command 0x0409 tx timeout