syzbot


BUG: sleeping function called from invalid context in do_con_write (2)

Status: upstream: reported C repro on 2021/02/22 12:46
Reported-by: syzbot+9a295b90a29984e591ea@syzkaller.appspotmail.com
First crash: 1218d, last: 479d
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 BUG: sleeping function called from invalid context in do_con_write 1 1430d 1430d 0/1 auto-closed as invalid on 2020/11/23 01:21
linux-4.19 BUG: sleeping function called from invalid context in do_con_write C error 67 500d 1215d 0/1 upstream: reported C repro on 2021/02/25 10:19
upstream BUG: sleeping function called from invalid context in do_con_write serial 1 1645d 1642d 0/27 auto-closed as invalid on 2020/04/21 23:47
Fix bisection attempts (14)
Created Duration User Patch Repo Result
2022/07/14 21:20 29m bisect fix linux-4.14.y job log (0) log
2022/06/14 20:45 27m bisect fix linux-4.14.y job log (0) log
2022/05/15 19:39 26m bisect fix linux-4.14.y job log (0) log
2022/04/15 19:05 22m bisect fix linux-4.14.y job log (0) log
2022/03/16 10:05 24m bisect fix linux-4.14.y job log (0) log
2022/02/14 09:41 23m bisect fix linux-4.14.y job log (0) log
2021/12/30 14:41 31m bisect fix linux-4.14.y job log (0) log
2021/11/30 14:11 24m bisect fix linux-4.14.y job log (0) log
2021/10/31 13:42 24m bisect fix linux-4.14.y job log (0) log
2021/10/01 12:55 23m bisect fix linux-4.14.y job log (0) log
2021/09/01 12:33 22m bisect fix linux-4.14.y job log (0) log
2021/07/19 05:55 23m bisect fix linux-4.14.y job log (0) log
2021/06/19 05:23 25m bisect fix linux-4.14.y job log (0) log
2021/05/20 04:34 22m bisect fix linux-4.14.y job log (0) log

Sample crash report:
BUG: sleeping function called from invalid context at drivers/tty/vt/vt.c:2245
in_atomic(): 1, irqs_disabled(): 1, pid: 8021, name: syz-executor388
3 locks held by syz-executor388/8021:
 #0:  (&tty->ldisc_sem){++++}, at: [<ffffffff8355c6a2>] tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:284
 #1:  (&(&gsm->control_lock)->rlock){....}, at: [<ffffffff83573016>] gsm_control_send+0xf6/0x480 drivers/tty/n_gsm.c:1434
 #2:  (&(&gsm->tx_lock)->rlock){....}, at: [<ffffffff83572e41>] gsm_data_queue drivers/tty/n_gsm.c:845 [inline]
 #2:  (&(&gsm->tx_lock)->rlock){....}, at: [<ffffffff83572e41>] gsm_control_transmit+0x1f1/0x2d0 drivers/tty/n_gsm.c:1375
irq event stamp: 13522
hardirqs last  enabled at (13521): [<ffffffff8724c959>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
hardirqs last  enabled at (13521): [<ffffffff8724c959>] _raw_spin_unlock_irqrestore+0x79/0xe0 kernel/locking/spinlock.c:192
hardirqs last disabled at (13522): [<ffffffff8724c5e6>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]
hardirqs last disabled at (13522): [<ffffffff8724c5e6>] _raw_spin_lock_irqsave+0x66/0xc0 kernel/locking/spinlock.c:160
softirqs last  enabled at (12268): [<ffffffff8760068b>] __do_softirq+0x68b/0x9ff kernel/softirq.c:314
softirqs last disabled at (11951): [<ffffffff81322d13>] invoke_softirq kernel/softirq.c:368 [inline]
softirqs last disabled at (11951): [<ffffffff81322d13>] irq_exit+0x193/0x240 kernel/softirq.c:409
Preemption disabled at:
[<          (null)>]           (null)
CPU: 0 PID: 8021 Comm: syz-executor388 Not tainted 4.14.301-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 ___might_sleep.cold+0x235/0x250 kernel/sched/core.c:6041
 do_con_write+0xd0/0x19b0 drivers/tty/vt/vt.c:2245
 con_write+0x21/0xa0 drivers/tty/vt/vt.c:2822
 gsmld_output+0xc3/0x190 drivers/tty/n_gsm.c:2312
 gsm_data_kick+0x266/0x9b0 drivers/tty/n_gsm.c:761
 gsm_data_queue drivers/tty/n_gsm.c:846 [inline]
 gsm_control_transmit+0x1ff/0x2d0 drivers/tty/n_gsm.c:1375
 gsm_control_send+0x38a/0x480 drivers/tty/n_gsm.c:1451
 gsm_disconnect drivers/tty/n_gsm.c:2110 [inline]
 gsmld_config.constprop.0+0x568/0xf90 drivers/tty/n_gsm.c:2636
 gsmld_ioctl+0x375/0x410 drivers/tty/n_gsm.c:2700
 tty_ioctl+0x5af/0x1430 drivers/tty/tty_io.c:2670
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:500 [inline]
 do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
 SYSC_ioctl fs/ioctl.c:701 [inline]
 SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7f01f64c6329
RSP: 002b:00007ffc8a358f88 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f01f64c6329
RDX: 0000000020000040 RSI: 00000000404c4701 RDI: 0000000000000005
RBP: 00007f01f648a1b0 R08: 000000000000000e R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f01f648a240
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000

========================================================
WARNING: possible irq lock inversion dependency detected
4.14.301-syzkaller #0 Tainted: G        W      
--------------------------------------------------------
ksoftirqd/0/7 just changed the state of lock:
 (&(&gsm->control_lock)->rlock){..-.}, at: [<ffffffff83573a95>] gsm_control_retransmit+0x25/0x2c0 drivers/tty/n_gsm.c:1394
but this lock took another, SOFTIRQ-unsafe lock in the past:
 (console_lock){+.+.}


and interrupts could create inverse lock ordering between them.


other info that might help us debug this:
Chain exists of:
  &(&gsm->control_lock)->rlock --> &(&gsm->tx_lock)->rlock --> console_lock

 Possible interrupt unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(console_lock);
                               local_irq_disable();
                               lock(&(&gsm->control_lock)->rlock);
                               lock(&(&gsm->tx_lock)->rlock);
  <Interrupt>
    lock(&(&gsm->control_lock)->rlock);

 *** DEADLOCK ***

1 lock held by ksoftirqd/0/7:
 #0:  (((&gsm->t2_timer))){+.-.}, at: [<ffffffff814871a8>] lockdep_copy_map include/linux/lockdep.h:174 [inline]
 #0:  (((&gsm->t2_timer))){+.-.}, at: [<ffffffff814871a8>] call_timer_fn+0xb8/0x650 kernel/time/timer.c:1270

the shortest dependencies between 2nd lock and 1st lock:
  -> (console_lock){+.+.} ops: 2763 {
     HARDIRQ-ON-W at:
                        lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
                        console_lock+0x42/0x70 kernel/printk/printk.c:2228
                        con_init+0x12/0x5d6 drivers/tty/vt/vt.c:3022
                        console_init+0x46/0x53 kernel/printk/printk.c:2809
                        start_kernel+0x521/0x763 init/main.c:638
                        secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:240
     SOFTIRQ-ON-W at:
                        lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
                        console_lock+0x42/0x70 kernel/printk/printk.c:2228
                        con_init+0x12/0x5d6 drivers/tty/vt/vt.c:3022
                        console_init+0x46/0x53 kernel/printk/printk.c:2809
                        start_kernel+0x521/0x763 init/main.c:638
                        secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:240
     INITIAL USE at:
   }
   ... key      at: [<ffffffff88f6f3e0>] console_lock_dep_map+0x0/0x40
   ... acquired at:
   console_lock+0x42/0x70 kernel/printk/printk.c:2228
   do_con_write+0xd5/0x19b0 drivers/tty/vt/vt.c:2247
   con_write+0x21/0xa0 drivers/tty/vt/vt.c:2822
   gsmld_output+0xc3/0x190 drivers/tty/n_gsm.c:2312
   gsm_data_kick+0x266/0x9b0 drivers/tty/n_gsm.c:761
   gsm_data_queue drivers/tty/n_gsm.c:846 [inline]
   gsm_control_transmit+0x1ff/0x2d0 drivers/tty/n_gsm.c:1375
   gsm_control_send+0x38a/0x480 drivers/tty/n_gsm.c:1451
   gsm_disconnect drivers/tty/n_gsm.c:2110 [inline]
   gsmld_config.constprop.0+0x568/0xf90 drivers/tty/n_gsm.c:2636
   gsmld_ioctl+0x375/0x410 drivers/tty/n_gsm.c:2700
   tty_ioctl+0x5af/0x1430 drivers/tty/tty_io.c:2670
   vfs_ioctl fs/ioctl.c:46 [inline]
   file_ioctl fs/ioctl.c:500 [inline]
   do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
   SYSC_ioctl fs/ioctl.c:701 [inline]
   SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
   do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
   entry_SYSCALL_64_after_hwframe+0x5e/0xd3

 -> (&(&gsm->tx_lock)->rlock){....} ops: 1 {
    INITIAL USE at:
                     lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
                     __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
                     _raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
                     gsm_data_queue drivers/tty/n_gsm.c:845 [inline]
                     gsm_control_transmit+0x1f1/0x2d0 drivers/tty/n_gsm.c:1375
                     gsm_control_send+0x38a/0x480 drivers/tty/n_gsm.c:1451
                     gsm_disconnect drivers/tty/n_gsm.c:2110 [inline]
                     gsmld_config.constprop.0+0x568/0xf90 drivers/tty/n_gsm.c:2636
                     gsmld_ioctl+0x375/0x410 drivers/tty/n_gsm.c:2700
                     tty_ioctl+0x5af/0x1430 drivers/tty/tty_io.c:2670
                     vfs_ioctl fs/ioctl.c:46 [inline]
                     file_ioctl fs/ioctl.c:500 [inline]
                     do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
                     SYSC_ioctl fs/ioctl.c:701 [inline]
                     SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
                     do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
                     entry_SYSCALL_64_after_hwframe+0x5e/0xd3
  }
  ... key      at: [<ffffffff8c8d3460>] __key.4+0x0/0x40
  ... acquired at:
   __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
   _raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
   gsm_data_queue drivers/tty/n_gsm.c:845 [inline]
   gsm_control_transmit+0x1f1/0x2d0 drivers/tty/n_gsm.c:1375
   gsm_control_send+0x38a/0x480 drivers/tty/n_gsm.c:1451
   gsm_disconnect drivers/tty/n_gsm.c:2110 [inline]
   gsmld_config.constprop.0+0x568/0xf90 drivers/tty/n_gsm.c:2636
   gsmld_ioctl+0x375/0x410 drivers/tty/n_gsm.c:2700
   tty_ioctl+0x5af/0x1430 drivers/tty/tty_io.c:2670
   vfs_ioctl fs/ioctl.c:46 [inline]
   file_ioctl fs/ioctl.c:500 [inline]
   do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
   SYSC_ioctl fs/ioctl.c:701 [inline]
   SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
   do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
   entry_SYSCALL_64_after_hwframe+0x5e/0xd3

-> (&(&gsm->control_lock)->rlock){..-.} ops: 2 {
   IN-SOFTIRQ-W at:
                    lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
                    __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
                    _raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
                    gsm_control_retransmit+0x25/0x2c0 drivers/tty/n_gsm.c:1394
                    call_timer_fn+0x14a/0x650 kernel/time/timer.c:1280
                    expire_timers+0x232/0x4d0 kernel/time/timer.c:1319
                    __run_timers kernel/time/timer.c:1637 [inline]
                    run_timer_softirq+0x1d5/0x5a0 kernel/time/timer.c:1650
                    __do_softirq+0x24d/0x9ff kernel/softirq.c:288
                    run_ksoftirqd+0x50/0x1a0 kernel/softirq.c:670
                    smpboot_thread_fn+0x5c1/0x920 kernel/smpboot.c:164
                    kthread+0x30d/0x420 kernel/kthread.c:232
                    ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406
   INITIAL USE at:
                   lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
                   __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
                   _raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
                   gsm_control_send+0xf6/0x480 drivers/tty/n_gsm.c:1434
                   gsm_disconnect drivers/tty/n_gsm.c:2110 [inline]
                   gsmld_config.constprop.0+0x568/0xf90 drivers/tty/n_gsm.c:2636
                   gsmld_ioctl+0x375/0x410 drivers/tty/n_gsm.c:2700
                   tty_ioctl+0x5af/0x1430 drivers/tty/tty_io.c:2670
                   vfs_ioctl fs/ioctl.c:46 [inline]
                   file_ioctl fs/ioctl.c:500 [inline]
                   do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
                   SYSC_ioctl fs/ioctl.c:701 [inline]
                   SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
                   do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
                   entry_SYSCALL_64_after_hwframe+0x5e/0xd3
 }
 ... key      at: [<ffffffff8c8d34a0>] __key.5+0x0/0x40
 ... acquired at:
   mark_lock_irq kernel/locking/lockdep.c:2804 [inline]
   mark_lock+0x3c7/0x1050 kernel/locking/lockdep.c:3194
   mark_irqflags kernel/locking/lockdep.c:3072 [inline]
   __lock_acquire+0xc81/0x3f20 kernel/locking/lockdep.c:3448
   lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
   __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
   _raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
   gsm_control_retransmit+0x25/0x2c0 drivers/tty/n_gsm.c:1394
   call_timer_fn+0x14a/0x650 kernel/time/timer.c:1280
   expire_timers+0x232/0x4d0 kernel/time/timer.c:1319
   __run_timers kernel/time/timer.c:1637 [inline]
   run_timer_softirq+0x1d5/0x5a0 kernel/time/timer.c:1650
   __do_softirq+0x24d/0x9ff kernel/softirq.c:288
   run_ksoftirqd+0x50/0x1a0 kernel/softirq.c:670
   smpboot_thread_fn+0x5c1/0x920 kernel/smpboot.c:164
   kthread+0x30d/0x420 kernel/kthread.c:232
   ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406


stack backtrace:
CPU: 0 PID: 7 Comm: ksoftirqd/0 Tainted: G        W       4.14.301-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 print_irq_inversion_bug.cold+0x313/0x346 kernel/locking/lockdep.c:2670
 check_usage_forwards+0x18f/0x2d0 kernel/locking/lockdep.c:2695
 mark_lock_irq kernel/locking/lockdep.c:2804 [inline]
 mark_lock+0x3c7/0x1050 kernel/locking/lockdep.c:3194
 mark_irqflags kernel/locking/lockdep.c:3072 [inline]
 __lock_acquire+0xc81/0x3f20 kernel/locking/lockdep.c:3448
 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
 gsm_control_retransmit+0x25/0x2c0 drivers/tty/n_gsm.c:1394
 call_timer_fn+0x14a/0x650 kernel/time/timer.c:1280
 expire_timers+0x232/0x4d0 kernel/time/timer.c:1319
 __run_timers kernel/time/timer.c:1637 [inline]
 run_timer_softirq+0x1d5/0x5a0 kernel/time/timer.c:1650
 __do_softirq+0x24d/0x9ff kernel/softirq.c:288
 run_ksoftirqd+0x50/0x1a0 kernel/softirq.c:670
 smpboot_thread_fn+0x5c1/0x920 kernel/smpboot.c:164
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406

Crashes (503):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/12/12 12:54 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2022/12/11 05:04 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2022/11/18 21:30 linux-4.14.y e911713e40ca 5bb70014 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2022/10/30 22:13 linux-4.14.y 41f36d7859a7 2a71366b .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2022/09/24 22:31 linux-4.14.y 4edbf74132a4 0042f2b4 .config console log report syz C [disk image] [vmlinux] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2022/08/27 14:03 linux-4.14.y e548869f356f 07177916 .config console log report syz C ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2022/08/09 21:49 linux-4.14.y b641242202ed c2a623d6 .config console log report syz C ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2021/08/02 12:32 linux-4.14.y ce4d1565392b 6c236867 .config console log report syz C ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2021/04/18 23:11 linux-4.14.y cf256fbcbe34 7e2b734b .config console log report syz C ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2021/03/18 04:12 linux-4.14.y cb83ddcd5332 fdb2bb2c .config console log report syz C ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2021/04/20 03:58 linux-4.14.y cf256fbcbe34 4285c989 .config console log report syz ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/03/03 18:18 linux-4.14.y 7878a41b6cc1 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/27 23:20 linux-4.14.y 7878a41b6cc1 95aee97a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/27 14:38 linux-4.14.y 7878a41b6cc1 9189cb53 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/27 12:21 linux-4.14.y 7878a41b6cc1 9189cb53 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/27 09:44 linux-4.14.y 7878a41b6cc1 9189cb53 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/26 07:17 linux-4.14.y 7878a41b6cc1 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/25 23:11 linux-4.14.y 7878a41b6cc1 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/25 15:37 linux-4.14.y 7878a41b6cc1 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/24 16:57 linux-4.14.y 1e61bd26fa2c ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/23 12:56 linux-4.14.y 1e61bd26fa2c 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/22 20:19 linux-4.14.y 1e61bd26fa2c 9f1e2cb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/22 16:46 linux-4.14.y 1e61bd26fa2c 9f1e2cb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/21 01:21 linux-4.14.y a8ad60f2af58 2414209c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/19 10:38 linux-4.14.y a8ad60f2af58 bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/18 14:00 linux-4.14.y a8ad60f2af58 d02e9a70 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/15 12:08 linux-4.14.y a8ad60f2af58 e62ba3c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/15 08:50 linux-4.14.y a8ad60f2af58 e62ba3c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/15 03:44 linux-4.14.y a8ad60f2af58 e62ba3c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/14 21:23 linux-4.14.y a8ad60f2af58 e62ba3c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/14 02:34 linux-4.14.y a8ad60f2af58 93ae7e0a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/13 19:13 linux-4.14.y a8ad60f2af58 957959cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/13 13:33 linux-4.14.y a8ad60f2af58 957959cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/13 07:48 linux-4.14.y a8ad60f2af58 93e26d60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/09 05:40 linux-4.14.y a8ad60f2af58 14a312c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/08 00:22 linux-4.14.y a8ad60f2af58 15c3d445 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/07 14:10 linux-4.14.y a8ad60f2af58 5bc3be51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/07 10:53 linux-4.14.y a8ad60f2af58 5bc3be51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/07 04:13 linux-4.14.y a8ad60f2af58 0a9c11b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/06 21:50 linux-4.14.y a8ad60f2af58 0a9c11b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/06 13:44 linux-4.14.y a8ad60f2af58 0a9c11b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/06 09:35 linux-4.14.y a8ad60f2af58 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/06 03:57 linux-4.14.y 3949d1610004 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/05 17:28 linux-4.14.y 3949d1610004 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/05 17:11 linux-4.14.y 3949d1610004 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/02/01 20:33 linux-4.14.y 3949d1610004 9a6f477c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/01/31 09:30 linux-4.14.y 3949d1610004 b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/01/31 01:50 linux-4.14.y 3949d1610004 b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/01/30 21:27 linux-4.14.y 3949d1610004 b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/01/30 13:23 linux-4.14.y 3949d1610004 b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/01/29 07:33 linux-4.14.y 3949d1610004 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/01/27 10:05 linux-4.14.y 3949d1610004 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/01/25 23:47 linux-4.14.y 3949d1610004 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2023/01/23 22:57 linux-4.14.y 97205fccccdc 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
2021/02/22 12:45 linux-4.14.y 29c52025152b a659b3f1 .config console log report info ci2-linux-4-14 BUG: sleeping function called from invalid context in do_con_write
* Struck through repros no longer work on HEAD.