audit: type=1400 audit(1663081248.704:8): avc: denied { kernel } for pid=3956 comm="syz-executor.6" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=perf_event permissive=1
------------[ cut here ]------------
======================================================
WARNING: possible circular locking dependency detected
6.0.0-rc5-next-20220913 #1 Not tainted
------------------------------------------------------
syz-executor.6/3957 is trying to acquire lock:
ffffffff853fa878 ((console_sem).lock){....}-{2:2}, at: down_trylock+0xe/0x70
but task is already holding lock:
ffff88800e1a1820 (&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
preempt_schedule_common+0x45/0xc0
__cond_resched+0x17/0x30
__mutex_lock+0xa3/0x14d0
__do_sys_perf_event_open+0x1eec/0x32c0
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+0x3f9e/0x6df0
kernel_clone+0xe7/0x890
user_mode_thread+0xad/0xf0
rest_init+0x24/0x250
arch_call_rest_init+0xf/0x14
start_kernel+0x4c1/0x4e6
secondary_startup_64_no_verify+0xe0/0xeb
-> #1 (&p->pi_lock){-.-.}-{2:2}:
_raw_spin_lock_irqsave+0x39/0x60
try_to_wake_up+0xab/0x1920
up+0x75/0xb0
__up_console_sem+0x6e/0x80
console_unlock+0x46a/0x590
vt_ioctl+0x2822/0x2ca0
tty_ioctl+0x7c4/0x1700
__x64_sys_ioctl+0x19a/0x210
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #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
preempt_schedule_common+0x45/0xc0
__cond_resched+0x17/0x30
__mutex_lock+0xa3/0x14d0
__do_sys_perf_event_open+0x1eec/0x32c0
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.6/3957:
#0: ffff88806ce37cd8 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x1cf/0x2470
#1: ffff88800e1a1820 (&ctx->lock){....}-{2:2}, at: __perf_event_task_sched_out+0x53b/0x18d0
stack backtrace:
CPU: 0 PID: 3957 Comm: syz-executor.6 Not tainted 6.0.0-rc5-next-20220913 #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 3b b7 ef ff e8 36 b7 ef ff 65 8b 1d ab 15 ac 7e 31 ff 89 de e8 d6 b3 ef ff 85 db 0f 84 8a 00 00 00 e8 19 b7 ef ff <0f> 0b e9 a5 fe ff ff e8 0d b7 ef ff 48 8d 7d 10 48 b8 00 00 00 00
RSP: 0018:ffff88803ff87978 EFLAGS: 00010006
RAX: 0000000040000002 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88801f9fd040 RSI: ffffffff81566027 RDI: 0000000000000005
RBP: ffff8880086605c8 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: ffffffff865aa01b R12: ffff88800e1a1800
R13: ffff88806ce3d100 R14: ffffffff8547c660 R15: 0000000000000002
ctx_sched_out+0x8f1/0xc10
__perf_event_task_sched_out+0x6d0/0x18d0
__schedule+0xedd/0x2470
preempt_schedule_common+0x45/0xc0
__cond_resched+0x17/0x30
__mutex_lock+0xa3/0x14d0
__do_sys_perf_event_open+0x1eec/0x32c0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6f48542b19
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:00007f6f45ab8188 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00007f6f48655f60 RCX: 00007f6f48542b19
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f6f4859cf6d R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcde6ea6bf R14: 00007f6f45ab8300 R15: 0000000000022000
WARNING: CPU: 0 PID: 3957 at kernel/events/core.c:2309 group_sched_out.part.0+0x2c7/0x460
Modules linked in:
CPU: 0 PID: 3957 Comm: syz-executor.6 Not tainted 6.0.0-rc5-next-20220913 #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 3b b7 ef ff e8 36 b7 ef ff 65 8b 1d ab 15 ac 7e 31 ff 89 de e8 d6 b3 ef ff 85 db 0f 84 8a 00 00 00 e8 19 b7 ef ff <0f> 0b e9 a5 fe ff ff e8 0d b7 ef ff 48 8d 7d 10 48 b8 00 00 00 00
RSP: 0018:ffff88803ff87978 EFLAGS: 00010006
RAX: 0000000040000002 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88801f9fd040 RSI: ffffffff81566027 RDI: 0000000000000005
RBP: ffff8880086605c8 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: ffffffff865aa01b R12: ffff88800e1a1800
R13: ffff88806ce3d100 R14: ffffffff8547c660 R15: 0000000000000002
FS: 00007f6f45ab8700(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efccc670820 CR3: 0000000015c5c000 CR4: 0000000000350ef0
Call Trace:
ctx_sched_out+0x8f1/0xc10
__perf_event_task_sched_out+0x6d0/0x18d0
__schedule+0xedd/0x2470
preempt_schedule_common+0x45/0xc0
__cond_resched+0x17/0x30
__mutex_lock+0xa3/0x14d0
__do_sys_perf_event_open+0x1eec/0x32c0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6f48542b19
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:00007f6f45ab8188 EFLAGS: 00000246 ORIG_RAX: 000000000000012a
RAX: ffffffffffffffda RBX: 00007f6f48655f60 RCX: 00007f6f48542b19
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f6f4859cf6d R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcde6ea6bf R14: 00007f6f45ab8300 R15: 0000000000022000
irq event stamp: 572
hardirqs last enabled at (571): [] _raw_spin_unlock_irqrestore+0x28/0x60
hardirqs last disabled at (572): [] __schedule+0x1225/0x2470
softirqs last enabled at (366): [] __irq_exit_rcu+0x11b/0x180
softirqs last disabled at (341): [] __irq_exit_rcu+0x11b/0x180
---[ end trace 0000000000000000 ]---
loop4: detected capacity change from 0 to 256
loop4: detected capacity change from 0 to 256
loop4: detected capacity change from 0 to 256
loop4: detected capacity change from 0 to 256
loop3: detected capacity change from 0 to 256
hrtimer: interrupt took 18565 ns
loop4: detected capacity change from 0 to 256
device lo entered promiscuous mode
capability: warning: `syz-executor.0' uses deprecated v2 capabilities in a way that may be insecure
9pnet_fd: p9_fd_create_tcp (4037): problem connecting socket to 127.0.0.1
loop3: detected capacity change from 0 to 256
audit: type=1400 audit(1663081249.461:9): avc: denied { write } for pid=4024 comm="syz-executor.5" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=perf_event permissive=1
device lo left promiscuous mode
device lo entered promiscuous mode
loop3: detected capacity change from 0 to 256
9pnet_fd: p9_fd_create_tcp (4037): problem connecting socket to 127.0.0.1
device lo left promiscuous mode
device lo entered promiscuous mode
device lo entered promiscuous mode
device lo entered promiscuous mode
device lo entered promiscuous mode
device lo left promiscuous mode
device lo left promiscuous mode
device lo entered promiscuous mode
device lo left promiscuous mode
device lo entered promiscuous mode
device lo left promiscuous mode
device lo entered promiscuous mode
device lo entered promiscuous mode
9pnet_fd: p9_fd_create_tcp (4082): problem connecting socket to 127.0.0.1
device lo left promiscuous mode
device lo entered promiscuous mode
device lo left promiscuous mode
device lo entered promiscuous mode
9pnet_fd: p9_fd_create_tcp (4076): problem connecting socket to 127.0.0.1
device lo left promiscuous mode
device lo entered promiscuous mode
9pnet_fd: p9_fd_create_tcp (4109): problem connecting socket to 127.0.0.1
9pnet_fd: p9_fd_create_tcp (4110): problem connecting socket to 127.0.0.1
9pnet_fd: p9_fd_create_tcp (4118): problem connecting socket to 127.0.0.1
9pnet_fd: p9_fd_create_tcp (4121): problem connecting socket to 127.0.0.1
9pnet_fd: p9_fd_create_tcp (4127): problem connecting socket to 127.0.0.1
No source specified
No source specified
No source specified
No source specified
9pnet_fd: p9_fd_create_tcp (4158): problem connecting socket to 127.0.0.1
No source specified
loop3: detected capacity change from 0 to 4096
EXT4-fs (loop3): mounted filesystem without journal. Quota mode: none.
EXT4-fs (loop3): unmounting filesystem.
loop7: detected capacity change from 0 to 40
loop3: detected capacity change from 0 to 4096
EXT4-fs (loop3): mounted filesystem without journal. Quota mode: none.
EXT4-fs (loop3): unmounting filesystem.
9pnet_fd: p9_fd_create_tcp (4179): problem connecting socket to 127.0.0.1
loop3: detected capacity change from 0 to 4096
EXT4-fs (loop3): mounted filesystem without journal. Quota mode: none.
EXT4-fs (loop3): unmounting filesystem.
syz-executor.7: attempt to access beyond end of device
loop7: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop7, logical block 10, lost async page write
syz-executor.7 (4195) used greatest stack depth: 24472 bytes left
loop0: detected capacity change from 0 to 5
=======================================================
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.
=======================================================
loop7: detected capacity change from 0 to 40
syz-executor.7: attempt to access beyond end of device
loop7: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop7, logical block 10, lost async page write
loop7: detected capacity change from 0 to 40
syz-executor.7: attempt to access beyond end of device
loop7: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop7, logical block 10, lost async page write
loop0: detected capacity change from 0 to 5
loop7: detected capacity change from 0 to 40
syz-executor.7: attempt to access beyond end of device
loop7: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop7, logical block 10, lost async page write
loop0: detected capacity change from 0 to 5
audit: type=1400 audit(1663081256.716:10): avc: denied { associate } for pid=4225 comm="syz-executor.7" name="/" dev="devpts" ino=1 scontext=system_u:object_r:shell_exec_t:s0 tcontext=system_u:object_r:devpts_t:s0 tclass=filesystem permissive=1
loop0: detected capacity change from 0 to 5
loop0: detected capacity change from 0 to 5
loop4: detected capacity change from 0 to 40
syz-executor.4: attempt to access beyond end of device
loop4: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop4, logical block 10, lost async page write
loop4: detected capacity change from 0 to 40
tc_dump_action: action bad kind
syz-executor.4: attempt to access beyond end of device
loop4: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop4, logical block 10, lost async page write
loop4: detected capacity change from 0 to 40
tc_dump_action: action bad kind
syz-executor.4: attempt to access beyond end of device
loop4: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop4, logical block 10, lost async page write
loop4: detected capacity change from 0 to 40
tc_dump_action: action bad kind
syz-executor.4: attempt to access beyond end of device
loop4: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop4, logical block 10, lost async page write
tc_dump_action: action bad kind