BUG: sleeping function called from invalid context at drivers/tty/vt/vt.c:2581 in_atomic(): 1, irqs_disabled(): 1, pid: 18903, name: syz-executor.5 3 locks held by syz-executor.5/18903: #0: 000000005af27a63 (&tty->ldisc_sem){++++}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:272 #1: 000000008f01c68e (&(&tty->flow_lock)->rlock){....}, at: spin_lock_irq include/linux/spinlock.h:354 [inline] #1: 000000008f01c68e (&(&tty->flow_lock)->rlock){....}, at: n_tty_ioctl_helper+0xcc/0x3a0 drivers/tty/tty_ioctl.c:914 #2: 000000005af27a63 (&tty->ldisc_sem){++++}, at: tty_ldisc_ref+0x1d/0x80 drivers/tty/tty_ldisc.c:293 irq event stamp: 402 hardirqs last enabled at (401): [] do_syscall_64+0x21/0x620 arch/x86/entry/common.c:280 hardirqs last disabled at (402): [] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:126 [inline] hardirqs last disabled at (402): [] _raw_spin_lock_irq+0x35/0x80 kernel/locking/spinlock.c:160 softirqs last enabled at (48): [] raw_hash_sk+0x1c4/0x250 net/ipv4/raw.c:107 softirqs last disabled at (46): [] raw_hash_sk+0xab/0x250 net/ipv4/raw.c:104 Preemption disabled at: [<0000000000000000>] (null) CPU: 0 PID: 18903 Comm: syz-executor.5 Not tainted 4.19.177-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 ___might_sleep.cold+0x235/0x250 kernel/sched/core.c:6192 do_con_write+0x116/0x1d90 drivers/tty/vt/vt.c:2581 con_write+0x22/0xb0 drivers/tty/vt/vt.c:3145 n_hdlc_send_frames+0x278/0x470 drivers/tty/n_hdlc.c:403 n_hdlc_tty_wakeup+0xa0/0xc0 drivers/tty/n_hdlc.c:479 tty_wakeup+0xd4/0x110 drivers/tty/tty_io.c:534 __start_tty drivers/tty/tty_io.c:806 [inline] __start_tty+0x116/0x150 drivers/tty/tty_io.c:799 n_tty_ioctl_helper+0x348/0x3a0 drivers/tty/tty_ioctl.c:917 n_hdlc_tty_ioctl+0x102/0x350 drivers/tty/n_hdlc.c:783 tty_ioctl+0x65d/0x15c0 drivers/tty/tty_io.c:2678 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x465ef9 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:00007faccf5db188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465ef9 RDX: 0000000000000001 RSI: 000000000000540a RDI: 0000000000000005 RBP: 00000000004bcd1c R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60 R13: 00007ffeb2fd8b3f R14: 00007faccf5db300 R15: 0000000000022000 capability: warning: `syz-executor.2' uses 32-bit capabilities (legacy support in use) F2FS-fs (loop5): Magic Mismatch, valid(0xf2f52010) - read(0x5377e300) F2FS-fs (loop5): Can't find valid F2FS filesystem in 1th superblock EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue F2FS-fs (loop5): Magic Mismatch, valid(0xf2f52010) - read(0x0) F2FS-fs (loop5): Can't find valid F2FS filesystem in 2th superblock F2FS-fs (loop5): Magic Mismatch, valid(0xf2f52010) - read(0x5377e300) F2FS-fs (loop5): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop5): Magic Mismatch, valid(0xf2f52010) - read(0x0) F2FS-fs (loop5): Can't find valid F2FS filesystem in 2th superblock F2FS-fs (loop5): Magic Mismatch, valid(0xf2f52010) - read(0x5377e300) F2FS-fs (loop5): Can't find valid F2FS filesystem in 1th superblock IPVS: Unknown mcast interface: virt_wifi0 tmpfs: No value for mount option 'dont_measure' tmpfs: No value for mount option 'dont_measure' IPVS: set_ctl: invalid protocol: 1 0.0.0.0:20003 IPVS: set_ctl: invalid protocol: 1 0.0.0.0:20003