syzbot


BUG: sleeping function called from invalid context in console_lock

Status: auto-obsoleted due to no activity on 2024/01/30 12:42
Reported-by: syzbot+028ba6e331e656006d3e@syzkaller.appspotmail.com
First crash: 336d, last: 187d
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) 10 6d05h 35d 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 865 now 403d 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 7110 35m 1054d 0/26 upstream: reported C repro on 2021/06/07 15:46
upstream BUG: sleeping function called from invalid context in console_lock serial 1 1440d 1440d 0/26 auto-closed as invalid on 2020/09/14 09:18

Sample crash report:
BUG: sleeping function called from invalid context at kernel/printk/printk.c:2549
in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 22860, name: syz-executor.0
3 locks held by syz-executor.0/22860:
 #0: ffff888090c99098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffff888090c99130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:961 [inline]
 #1: ffff888090c99130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:984 [inline]
 #1: ffff888090c99130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write+0x24f/0x920 drivers/tty/tty_io.c:1110
 #2: ffff888090c9b398 (&gsm->tx_lock){....}-{2:2}, at: gsmld_write+0x5b/0x120 drivers/tty/n_gsm.c:2926
irq event stamp: 46
hardirqs last  enabled at (45): [<ffffffff8a2418fb>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
hardirqs last  enabled at (45): [<ffffffff8a2418fb>] _raw_spin_unlock_irqrestore+0x8b/0x130 kernel/locking/spinlock.c:194
hardirqs last disabled at (46): [<ffffffff8a24166c>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]
hardirqs last disabled at (46): [<ffffffff8a24166c>] _raw_spin_lock_irqsave+0xac/0x120 kernel/locking/spinlock.c:162
softirqs last  enabled at (0): [<ffffffff814b26b9>] copy_process+0x13b9/0x3ef0 kernel/fork.c:2151
softirqs last disabled at (0): [<0000000000000000>] 0x0
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 1 PID: 22860 Comm: syz-executor.0 Not tainted 5.15.136-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 ___might_sleep+0x547/0x6a0 kernel/sched/core.c:9620
 console_lock+0x18/0x70 kernel/printk/printk.c:2549
 do_con_write+0x110/0x7270 drivers/tty/vt/vt.c:2908
 con_write+0x20/0x40 drivers/tty/vt/vt.c:3295
 gsmld_write+0xf9/0x120 drivers/tty/n_gsm.c:2929
 do_tty_write drivers/tty/tty_io.c:1038 [inline]
 file_tty_write+0x561/0x920 drivers/tty/tty_io.c:1110
 do_iter_readv_writev+0x594/0x7a0
 do_iter_write+0x1ea/0x760 fs/read_write.c:855
 vfs_writev fs/read_write.c:928 [inline]
 do_writev+0x281/0x470 fs/read_write.c:971
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fd0715c6ae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd06fb270c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 00007fd0716e6050 RCX: 00007fd0715c6ae9
RDX: 0000000000000006 RSI: 00000000200003c0 RDI: 0000000000000003
RBP: 00007fd07161247a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fd0716e6050 R15: 00007ffe68422f68
 </TASK>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/10/22 12:41 linux-5.15.y 00c03985402e 361b23dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: sleeping function called from invalid context in console_lock
2023/08/23 12:26 linux-5.15.y f6f7927ac664 b81ca3f6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: sleeping function called from invalid context in console_lock
2023/05/26 07:51 linux-5.15.y 1fe619a7d252 b40ef614 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: sleeping function called from invalid context in console_lock
2023/08/23 11:53 linux-5.15.y f6f7927ac664 b81ca3f6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: sleeping function called from invalid context in console_lock
* Struck through repros no longer work on HEAD.