syzbot


BUG: sleeping function called from invalid context in console_lock

Status: auto-closed as invalid on 2020/09/14 09:18
Subsystems: serial
[Documentation on labels]
Reported-by: syzbot+f8589c355cdce42b2446@syzkaller.appspotmail.com
First crash: 1411d, last: 1411d
Discussions (1)
Title Replies (including bot) Last reply
BUG: sleeping function called from invalid context in console_lock 0 (1) 2020/05/18 01:22
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 BUG: sleeping function called from invalid context in console_lock (2) 2 1d01h 6d21h 0/3 upstream: reported on 2024/03/22 09:16
linux-6.1 BUG: sleeping function called from invalid context in console_lock origin:upstream C 609 now 374d 0/3 upstream: reported C repro on 2023/03/20 10:28
upstream BUG: sleeping function called from invalid context in console_lock (2) serial C inconclusive inconclusive 5424 15m 1025d 0/26 upstream: reported C repro on 2021/06/07 15:46
linux-5.15 BUG: sleeping function called from invalid context in console_lock 4 158d 307d 0/3 auto-obsoleted due to no activity on 2024/01/30 12:42

Sample crash report:
BUG: sleeping function called from invalid context at kernel/printk/printk.c:2312
in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 21174, name: syz-executor.5
3 locks held by syz-executor.5/21174:
 #0: ffff8880a965c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:267
 #1: ffff8880a965c3f8 (&tty->flow_lock){....}-{2:2}, at: spin_lock_irq include/linux/spinlock.h:378 [inline]
 #1: ffff8880a965c3f8 (&tty->flow_lock){....}-{2:2}, at: n_tty_ioctl_helper drivers/tty/tty_ioctl.c:914 [inline]
 #1: ffff8880a965c3f8 (&tty->flow_lock){....}-{2:2}, at: n_tty_ioctl_helper+0xcc/0x3b0 drivers/tty/tty_ioctl.c:894
 #2: ffff8880a965c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref+0x1d/0x80 drivers/tty/tty_ldisc.c:288
irq event stamp: 46
hardirqs last  enabled at (45): [<ffffffff81b0ba8b>] kfree+0x1eb/0x2b0 mm/slab.c:3758
hardirqs last disabled at (46): [<ffffffff87d08f35>] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:126 [inline]
hardirqs last disabled at (46): [<ffffffff87d08f35>] _raw_spin_lock_irq+0x35/0x80 kernel/locking/spinlock.c:167
softirqs last  enabled at (0): [<ffffffff8143deb7>] copy_process+0x1ae7/0x7110 kernel/fork.c:2031
softirqs last disabled at (0): [<0000000000000000>] 0x0
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 0 PID: 21174 Comm: syz-executor.5 Not tainted 5.7.0-rc5-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+0x188/0x20d lib/dump_stack.c:118
 ___might_sleep.cold+0x1f4/0x23d kernel/sched/core.c:6801
 console_lock+0x19/0x80 kernel/printk/printk.c:2312
 do_con_write.part.0+0x95/0x1dc0 drivers/tty/vt/vt.c:2596
 do_con_write drivers/tty/vt/vt.c:2593 [inline]
 con_write+0x41/0xe0 drivers/tty/vt/vt.c:3159
 n_hdlc_send_frames+0x22d/0x3d0 drivers/tty/n_hdlc.c:289
 tty_wakeup+0xe1/0x120 drivers/tty/tty_io.c:536
 __start_tty+0x5c/0x70 drivers/tty/tty_io.c:803
 n_tty_ioctl_helper drivers/tty/tty_ioctl.c:917 [inline]
 n_tty_ioctl_helper+0x34e/0x3b0 drivers/tty/tty_ioctl.c:894
 n_hdlc_tty_ioctl+0xd3/0x2f0 drivers/tty/n_hdlc.c:615
 tty_ioctl+0xf88/0x1440 drivers/tty/tty_io.c:2665
 tty_compat_ioctl+0x2bf/0x410 drivers/tty/tty_io.c:2834
 __do_compat_sys_ioctl fs/ioctl.c:865 [inline]
 __se_compat_sys_ioctl fs/ioctl.c:816 [inline]
 __ia32_compat_sys_ioctl+0x23d/0x2b0 fs/ioctl.c:816
 do_syscall_32_irqs_on arch/x86/entry/common.c:337 [inline]
 do_fast_syscall_32+0x270/0xe90 arch/x86/entry/common.c:396
 entry_SYSENTER_compat+0x70/0x7f arch/x86/entry/entry_64_compat.S:139

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/05/17 09:17 upstream 3d1c1e5931ce 37bccd4e .config console log report ci-upstream-kasan-gce-386
* Struck through repros no longer work on HEAD.