ci starts bisection 2023-05-08 02:08:43.678399122 +0000 UTC m=+162353.940050948 bisecting fixing commit since 1a61b828566fba088d3baa0dc3e440b51fdf9ce2 building syzkaller on 0042f2b4c00ce1ceeaa44a0147909fe3a6f86c5c ensuring issue is reproducible on original commit 1a61b828566fba088d3baa0dc3e440b51fdf9ce2 testing commit 1a61b828566fba088d3baa0dc3e440b51fdf9ce2 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: a14da51dcb1ad9516610c70ca66a4f99d3767c7bb0ef078ae661432680c2d366 all runs: crashed: BUG: sleeping function called from invalid context in gsm_send testing current HEAD ac9a78681b921877518763ba0e89202254349d1b testing commit ac9a78681b921877518763ba0e89202254349d1b gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 50123fb7e02c32743e9ea361f6e0d67044de926fe02481d163060d104ebee693 all runs: crashed: BUG: sleeping function called from invalid context in console_lock crash still not fixed/happens on the oldest tested release revisions tested: 2, total time: 31m16.971993273s (build: 19m32.420578431s, test: 10m27.07109542s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Linux 6.4-rc1 crash: BUG: sleeping function called from invalid context in console_lock BUG: sleeping function called from invalid context at kernel/printk/printk.c:2598 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 4363, name: kworker/1:3 preempt_count: 1, expected: 0 RCU nest depth: 0, expected: 0 3 locks held by kworker/1:3/4363: #0: ffff888010c70d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline] #0: ffff888010c70d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline] #0: ffff888010c70d38 ((wq_completion)events){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1324 [inline] #0: ffff888010c70d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:643 [inline] #0: ffff888010c70d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:670 [inline] #0: ffff888010c70d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x793/0x1410 kernel/workqueue.c:2376 #1: ffffc9000532fdc0 ((work_completion)(&gsm->tx_work)){+.+.}-{0:0}, at: process_one_work+0x7c0/0x1410 kernel/workqueue.c:2380 #2: ffff88801eedd3e0 (&gsm->tx_lock){....}-{2:2}, at: gsmld_write_task+0x2c/0xd60 drivers/tty/n_gsm.c:3444 irq event stamp: 4790 hardirqs last enabled at (4789): [] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline] hardirqs last enabled at (4789): [] _raw_spin_unlock_irq+0x1f/0x40 kernel/locking/spinlock.c:202 hardirqs last disabled at (4790): [] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline] hardirqs last disabled at (4790): [] _raw_spin_lock_irqsave+0x4e/0x50 kernel/locking/spinlock.c:162 softirqs last enabled at (4782): [] do_softirq.part.0+0xde/0x130 kernel/softirq.c:472 softirqs last disabled at (4759): [] do_softirq.part.0+0xde/0x130 kernel/softirq.c:472 Preemption disabled at: [<0000000000000000>] 0x0 CPU: 1 PID: 4363 Comm: kworker/1:3 Not tainted 6.4.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023 Workqueue: events gsmld_write_task Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x60/0xa0 lib/dump_stack.c:106 __might_resched+0x354/0x580 kernel/sched/core.c:10153 console_lock+0x11/0x60 kernel/printk/printk.c:2598 do_con_write+0xf2/0x19c0 drivers/tty/vt/vt.c:2863 con_write+0xb/0x20 drivers/tty/vt/vt.c:3246 gsmld_output drivers/tty/n_gsm.c:3411 [inline] gsm_send_packet+0x35d/0x940 drivers/tty/n_gsm.c:962 gsm_data_kick drivers/tty/n_gsm.c:1024 [inline] gsmld_write_task+0x1d6/0xd60 drivers/tty/n_gsm.c:3446 process_one_work+0x86e/0x1410 kernel/workqueue.c:2405 worker_thread+0x5ab/0xef0 kernel/workqueue.c:2552 kthread+0x2e6/0x3c0 kernel/kthread.c:379 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308