syzbot


BUG: sleeping function called from invalid context in console_lock_spinning_enable

Status: auto-obsoleted due to no activity on 2024/04/05 00:14
Reported-by: syzbot+b4ba5528524b199c9456@syzkaller.appspotmail.com
First crash: 342d, last: 342d

Sample crash report:
BUG: sleeping function called from invalid context at kernel/printk/printk.c:2588
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 1 PID: 15729 Comm: syz-executor.5 Not tainted 6.1.69-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 lookup_chain_cache_add kernel/locking/lockdep.c:3772 [inline]
 validate_chain kernel/locking/lockdep.c:3793 [inline]
 __lock_acquire+0x1b88/0x7680 kernel/locking/lockdep.c:5049
 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662
 console_lock_spinning_enable+0x68/0x78 kernel/printk/printk.c:1805
 console_emit_next_record+0x7e4/0xb40 kernel/printk/printk.c:2739
 console_unlock+0x294/0x698 kernel/printk/printk.c:2871
 vprintk_emit+0x150/0x2e8 kernel/printk/printk.c:2268
 vprintk_default+0xa0/0xe4 kernel/printk/printk.c:2283
 vprintk+0x200/0x2d4 kernel/printk/printk_safe.c:45
 _printk+0xdc/0x128 kernel/printk/printk.c:2293
 __might_resched+0x268/0x4d8 kernel/sched/core.c:9919
 __might_sleep+0x90/0xe4 kernel/sched/core.c:9871
 console_lock+0x38/0x238 kernel/printk/printk.c:2588
 do_con_write+0x110/0x5a90 drivers/tty/vt/vt.c:2908
 con_write+0x34/0x58 drivers/tty/vt/vt.c:3295
 gsmld_write+0x104/0x154 drivers/tty/n_gsm.c:3060
 do_tty_write drivers/tty/tty_io.c:1018 [inline]
 file_tty_write+0x404/0x6f0 drivers/tty/tty_io.c:1089
 tty_write+0x48/0x58 drivers/tty/tty_io.c:1110
 call_write_iter include/linux/fs.h:2248 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x610/0x914 fs/read_write.c:584
 ksys_write+0x15c/0x26c fs/read_write.c:637
 __do_sys_write fs/read_write.c:649 [inline]
 __se_sys_write fs/read_write.c:646 [inline]
 __arm64_sys_write+0x7c/0x90 fs/read_write.c:646
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 15729, name: syz-executor.5
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
irq event stamp: 142
hardirqs last  enabled at (141): [<ffff8000121438b8>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:84 [inline]
hardirqs last  enabled at (141): [<ffff8000121438b8>] exit_to_kernel_mode+0xe8/0x118 arch/arm64/kernel/entry-common.c:94
hardirqs last disabled at (142): [<ffff8000122259c0>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]
hardirqs last disabled at (142): [<ffff8000122259c0>] _raw_spin_lock_irqsave+0xa4/0xb4 kernel/locking/spinlock.c:162
softirqs last  enabled at (130): [<ffff800008033064>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (128): [<ffff800008033030>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
Preemption disabled at:
[<ffff80000b5f8884>] gsmld_write+0x60/0x154 drivers/tty/n_gsm.c:3057
CPU: 1 PID: 15729 Comm: syz-executor.5 Not tainted 6.1.69-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 __might_resched+0x37c/0x4d8 kernel/sched/core.c:9942
 __might_sleep+0x90/0xe4 kernel/sched/core.c:9871
 console_lock+0x38/0x238 kernel/printk/printk.c:2588
 do_con_write+0x110/0x5a90 drivers/tty/vt/vt.c:2908
 con_write+0x34/0x58 drivers/tty/vt/vt.c:3295
 gsmld_write+0x104/0x154 drivers/tty/n_gsm.c:3060
 do_tty_write drivers/tty/tty_io.c:1018 [inline]
 file_tty_write+0x404/0x6f0 drivers/tty/tty_io.c:1089
 tty_write+0x48/0x58 drivers/tty/tty_io.c:1110
 call_write_iter include/linux/fs.h:2248 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x610/0x914 fs/read_write.c:584
 ksys_write+0x15c/0x26c fs/read_write.c:637
 __do_sys_write fs/read_write.c:649 [inline]
 __se_sys_write fs/read_write.c:646 [inline]
 __arm64_sys_write+0x7c/0x90 fs/read_write.c:646
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/12/27 00:13 linux-6.1.y 4aa6747d9352 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: sleeping function called from invalid context in console_lock_spinning_enable
* Struck through repros no longer work on HEAD.