------------[ cut here ]------------
======================================================
WARNING: possible circular locking dependency detected
6.0.0-rc7-next-20220927 #1 Not tainted
------------------------------------------------------
syz-executor.7/4031 is trying to acquire lock:
ffffffff853faab8 ((console_sem).lock){....}-{2:2}, at: down_trylock+0xe/0x70
but task is already holding lock:
ffff88800ea55c20 (&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
exit_to_user_mode_prepare+0x114/0x1a0
irqentry_exit_to_user_mode+0x5/0x30
asm_sysvec_apic_timer_interrupt+0x16/0x20
-> #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
do_con_write+0xc05/0x1d50
con_write+0x21/0x40
n_tty_write+0x4d4/0xfe0
file_tty_write.constprop.0+0x455/0x8a0
vfs_write+0x9c3/0xd90
ksys_write+0x127/0x250
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
schedule+0xda/0x1b0
exit_to_user_mode_prepare+0x114/0x1a0
irqentry_exit_to_user_mode+0x5/0x30
asm_sysvec_apic_timer_interrupt+0x16/0x20
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.7/4031:
#0: ffff88806ce37d18 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x1cf/0x2470
#1: ffff88800ea55c20 (&ctx->lock){....}-{2:2}, at: __perf_event_task_sched_out+0x53b/0x18d0
stack backtrace:
CPU: 0 PID: 4031 Comm: syz-executor.7 Not tainted 6.0.0-rc7-next-20220927 #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 ab a9 ef ff e8 a6 a9 ef ff 65 8b 1d 1b 0f ac 7e 31 ff 89 de e8 46 a6 ef ff 85 db 0f 84 8a 00 00 00 e8 89 a9 ef ff <0f> 0b e9 a5 fe ff ff e8 7d a9 ef ff 48 8d 7d 10 48 b8 00 00 00 00
RSP: 0000:ffff88801b207c68 EFLAGS: 00010006
RAX: 0000000040000002 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88803e048000 RSI: ffffffff815666b7 RDI: 0000000000000005
RBP: ffff8880086605c8 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: ffffffff865b401b R12: ffff88800ea55c00
R13: ffff88806ce3d140 R14: ffffffff85480400 R15: 0000000000000002
ctx_sched_out+0x8f1/0xc10
__perf_event_task_sched_out+0x6d0/0x18d0
__schedule+0xedd/0x2470
schedule+0xda/0x1b0
exit_to_user_mode_prepare+0x114/0x1a0
irqentry_exit_to_user_mode+0x5/0x30
asm_sysvec_apic_timer_interrupt+0x16/0x20
RIP: 0033:0x7f8c49a0a5b7
Code: e2 c6 f8 ff eb cc 0f 1f 44 00 00 0f bf 06 8b 15 83 19 13 00 39 d0 74 ba 0f b7 d2 66 89 16 eb b2 0f 1f 00 48 c7 c0 bc ff ff ff <64> 48 03 04 25 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f
RSP: 002b:00007f8c46fcc198 EFLAGS: 00000246
RAX: ffffffffffffffbc RBX: 00007f8c49b69f60 RCX: 00007f8c49b69f60
RDX: 0000000000000000 RSI: 00007f8c499fd42e RDI: 00000000200000c0
RBP: 00007f8c49ab0f6d R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff4bfed53f R14: 00007f8c46fcc300 R15: 0000000000022000
WARNING: CPU: 0 PID: 4031 at kernel/events/core.c:2309 group_sched_out.part.0+0x2c7/0x460
Modules linked in:
CPU: 0 PID: 4031 Comm: syz-executor.7 Not tainted 6.0.0-rc7-next-20220927 #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 ab a9 ef ff e8 a6 a9 ef ff 65 8b 1d 1b 0f ac 7e 31 ff 89 de e8 46 a6 ef ff 85 db 0f 84 8a 00 00 00 e8 89 a9 ef ff <0f> 0b e9 a5 fe ff ff e8 7d a9 ef ff 48 8d 7d 10 48 b8 00 00 00 00
RSP: 0000:ffff88801b207c68 EFLAGS: 00010006
RAX: 0000000040000002 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88803e048000 RSI: ffffffff815666b7 RDI: 0000000000000005
RBP: ffff8880086605c8 R08: 0000000000000005 R09: 0000000000000001
R10: 0000000000000000 R11: ffffffff865b401b R12: ffff88800ea55c00
R13: ffff88806ce3d140 R14: ffffffff85480400 R15: 0000000000000002
FS: 00007f8c46fcc700(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2c123000 CR3: 000000003d94c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
ctx_sched_out+0x8f1/0xc10
__perf_event_task_sched_out+0x6d0/0x18d0
__schedule+0xedd/0x2470
schedule+0xda/0x1b0
exit_to_user_mode_prepare+0x114/0x1a0
irqentry_exit_to_user_mode+0x5/0x30
asm_sysvec_apic_timer_interrupt+0x16/0x20
RIP: 0033:0x7f8c49a0a5b7
Code: e2 c6 f8 ff eb cc 0f 1f 44 00 00 0f bf 06 8b 15 83 19 13 00 39 d0 74 ba 0f b7 d2 66 89 16 eb b2 0f 1f 00 48 c7 c0 bc ff ff ff <64> 48 03 04 25 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f
RSP: 002b:00007f8c46fcc198 EFLAGS: 00000246
RAX: ffffffffffffffbc RBX: 00007f8c49b69f60 RCX: 00007f8c49b69f60
RDX: 0000000000000000 RSI: 00007f8c499fd42e RDI: 00000000200000c0
RBP: 00007f8c49ab0f6d R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff4bfed53f R14: 00007f8c46fcc300 R15: 0000000000022000
irq event stamp: 432
hardirqs last enabled at (431): [] exit_to_user_mode_prepare+0x109/0x1a0
hardirqs last disabled at (432): [] __schedule+0x1225/0x2470
softirqs last enabled at (270): [] toggle_bp_slot.constprop.0+0x29ff/0x2f80
softirqs last disabled at (268): [] toggle_bp_slot.constprop.0+0x134b/0x2f80
---[ end trace 0000000000000000 ]---
loop5: detected capacity change from 0 to 2560
EXT4-fs (loop5): mounted filesystem without journal. Quota mode: none.
ext4 filesystem being mounted at /syzkaller-testdir542466378/syzkaller.x2FsQm/3/file0 supports timestamps until 2038 (0x7fffffff)
EXT4-fs (loop5): unmounting filesystem.
Bluetooth: Unexpected continuation frame (len 11)
Bluetooth: hci1: Malformed Event: 0x02
Bluetooth: Unexpected continuation frame (len 11)
Bluetooth: hci1: Malformed Event: 0x02
Bluetooth: Unexpected continuation frame (len 11)
Bluetooth: hci1: Malformed Event: 0x02
Bluetooth: Unexpected continuation frame (len 11)
Bluetooth: hci1: Malformed Event: 0x02
Bluetooth: Unexpected continuation frame (len 11)
Bluetooth: hci1: Malformed Event: 0x02
loop6: detected capacity change from 0 to 256
FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
autofs4:pid:4127:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4127:check_dev_ioctl_version: ioctl control interface version mismatch: kernel(1.1), user(1768304430.3237228), cmd(0xc0189376)
autofs4:pid:4127:validate_dev_ioctl: invalid device control module version supplied for cmd(0xc0189376)
autofs4:pid:4145:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
loop6: detected capacity change from 0 to 256
autofs4:pid:4148:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
hrtimer: interrupt took 18254 ns
autofs4:pid:4168:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
autofs4:pid:4181:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4182:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4173:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4176:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
loop6: detected capacity change from 0 to 256
FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
autofs4:pid:4197:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4199:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4194:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4198:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4200:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4201:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4204:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4205:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4210:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4209:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4212:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4214:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4221:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4218:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4224:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4219:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4225:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
loop6: detected capacity change from 0 to 256
loop6: detected capacity change from 0 to 256
FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop3: detected capacity change from 0 to 256
autofs4:pid:4233:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
autofs4:pid:4231:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4240:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4241:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
autofs4:pid:4242:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
loop4: detected capacity change from 0 to 256
FAT-fs (loop4): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop3: detected capacity change from 0 to 256
autofs4:pid:4247:validate_dev_ioctl: path string terminator missing for cmd(0xc0189376)
FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop5: detected capacity change from 0 to 256
FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop4: detected capacity change from 0 to 256
loop5: detected capacity change from 0 to 256
FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
FAT-fs (loop4): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop3: detected capacity change from 0 to 256
FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop2: detected capacity change from 0 to 256
FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy
misc raw-gadget: fail, usb_gadget_register_driver returned -16
loop5: detected capacity change from 0 to 256
FAT-fs (loop5): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop2: detected capacity change from 0 to 256
FAT-fs (loop2): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)
loop4: detected capacity change from 0 to 256
UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy
misc raw-gadget: fail, usb_gadget_register_driver returned -16
loop6: detected capacity change from 0 to 256
FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)