syzbot


possible deadlock in console_unlock

Status: upstream: reported C repro on 2019/04/16 05:13
Reported-by: syzbot+0cef9b2d4438ff3a6c8d@syzkaller.appspotmail.com
First crash: 2047d, last: 630d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in console_unlock C done 22098 1108d 2360d 28/28 closed as dup on 2021/01/21 05:31
linux-4.19 possible deadlock in console_unlock C 5771 629d 2051d 0/1 upstream: reported C repro on 2019/04/11 15:05
upstream possible deadlock in console_unlock (2) serial C error done 599 653d 1103d 22/28 fixed on 2023/02/24 13:51
android-414 possible deadlock in console_unlock C 5 2086d 2051d 0/1 public: reported C repro on 2019/04/12 00:01
Fix bisection attempts (6)
Created Duration User Patch Repo Result
2021/11/16 10:34 21m bisect fix linux-4.14.y OK (0) job log log
2021/10/17 10:10 21m bisect fix linux-4.14.y OK (0) job log log
2021/09/17 09:43 26m bisect fix linux-4.14.y OK (0) job log log
2021/08/18 09:15 27m bisect fix linux-4.14.y OK (0) job log log
2021/07/19 08:52 23m bisect fix linux-4.14.y OK (0) job log log
2021/06/19 08:27 24m bisect fix linux-4.14.y OK (0) job log log

Sample crash report:
RDX: 0000000000000002 RSI: 000000000000540a RDI: 0000000000000003
RBP: 00007ffcb2860640 R08: 0000000000000001 R09: 00007f6d27fc0031
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
======================================================
WARNING: possible circular locking dependency detected
4.14.305-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor406/7987 is trying to acquire lock:
 (console_owner){....}, at: [<ffffffff81440a17>] log_next kernel/printk/printk.c:495 [inline]
 (console_owner){....}, at: [<ffffffff81440a17>] console_unlock+0x307/0xf20 kernel/printk/printk.c:2396

but task is already holding lock:
 (&(&port->lock)->rlock){-.-.}, at: [<ffffffff83560b1b>] tty_insert_flip_string_and_push_buffer+0x2b/0x160 drivers/tty/tty_buffer.c:569

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&(&port->lock)->rlock){-.-.}:
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
       tty_port_tty_get+0x1d/0x80 drivers/tty/tty_port.c:288
       tty_port_default_wakeup+0x11/0x40 drivers/tty/tty_port.c:46
       serial8250_tx_chars+0x3fe/0xc70 drivers/tty/serial/8250/8250_port.c:1828
       serial8250_handle_irq.part.0+0x2c7/0x390 drivers/tty/serial/8250/8250_port.c:1918
       serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1891 [inline]
       serial8250_default_handle_irq+0x8a/0x1f0 drivers/tty/serial/8250/8250_port.c:1934
       serial8250_interrupt+0xf3/0x210 drivers/tty/serial/8250/8250_core.c:129
       __handle_irq_event_percpu+0xee/0x7f0 kernel/irq/handle.c:147
       handle_irq_event_percpu kernel/irq/handle.c:187 [inline]
       handle_irq_event+0xed/0x240 kernel/irq/handle.c:204
       handle_edge_irq+0x224/0xc40 kernel/irq/chip.c:770
       generic_handle_irq_desc include/linux/irqdesc.h:159 [inline]
       handle_irq+0x35/0x50 arch/x86/kernel/irq_64.c:87
       do_IRQ+0x93/0x1d0 arch/x86/kernel/irq.c:230
       ret_from_intr+0x0/0x1e
       native_safe_halt+0xe/0x10 arch/x86/include/asm/irqflags.h:60
       arch_safe_halt arch/x86/include/asm/paravirt.h:94 [inline]
       default_idle+0x47/0x370 arch/x86/kernel/process.c:558
       cpuidle_idle_call kernel/sched/idle.c:156 [inline]
       do_idle+0x250/0x3c0 kernel/sched/idle.c:246
       cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:351
       start_kernel+0x743/0x763 init/main.c:712
       secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:240

-> #1 (&port_lock_key){-.-.}:
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
       serial8250_console_write+0x8cb/0xb40 drivers/tty/serial/8250/8250_port.c:3281
       call_console_drivers kernel/printk/printk.c:1727 [inline]
       console_unlock+0x99d/0xf20 kernel/printk/printk.c:2409
       vprintk_emit+0x224/0x620 kernel/printk/printk.c:1925
       vprintk_func+0x58/0x160 kernel/printk/printk_safe.c:409
       printk+0x9e/0xbc kernel/printk/printk.c:1998
       register_console+0x6f4/0xad0 kernel/printk/printk.c:2728
       univ8250_console_init+0x2f/0x3a drivers/tty/serial/8250/8250_core.c:691
       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

-> #0 (console_owner){....}:
       lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
       console_lock_spinning_enable kernel/printk/printk.c:1590 [inline]
       console_unlock+0x36f/0xf20 kernel/printk/printk.c:2406
       vprintk_emit+0x224/0x620 kernel/printk/printk.c:1925
       vprintk_func+0x58/0x160 kernel/printk/printk_safe.c:409
       printk+0x9e/0xbc kernel/printk/printk.c:1998
       fail_dump lib/fault-inject.c:44 [inline]
       should_fail.cold+0xdf/0x149 lib/fault-inject.c:149
       should_failslab+0xd6/0x130 mm/failslab.c:32
       slab_pre_alloc_hook mm/slab.h:421 [inline]
       slab_alloc mm/slab.c:3376 [inline]
       __do_kmalloc mm/slab.c:3718 [inline]
       __kmalloc+0x6d/0x400 mm/slab.c:3729
       kmalloc include/linux/slab.h:493 [inline]
       tty_buffer_alloc+0xc0/0x270 drivers/tty/tty_buffer.c:169
       __tty_buffer_request_room+0x12c/0x290 drivers/tty/tty_buffer.c:268
       tty_insert_flip_string_fixed_flag+0x8b/0x210 drivers/tty/tty_buffer.c:313
       tty_insert_flip_string include/linux/tty_flip.h:36 [inline]
       tty_insert_flip_string_and_push_buffer+0x3e/0x160 drivers/tty/tty_buffer.c:570
       pty_write+0xc3/0xf0 drivers/tty/pty.c:118
       tty_send_xchar+0x245/0x360 drivers/tty/tty_io.c:1092
       n_tty_ioctl_helper+0x145/0x350 drivers/tty/tty_ioctl.c:926
       n_tty_ioctl+0x47/0x2e0 drivers/tty/n_tty.c:2466
       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

other info that might help us debug this:

Chain exists of:
  console_owner --> &port_lock_key --> &(&port->lock)->rlock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&(&port->lock)->rlock);
                               lock(&port_lock_key);
                               lock(&(&port->lock)->rlock);
  lock(console_owner);

 *** DEADLOCK ***

5 locks held by syz-executor406/7987:
 #0:  (&tty->ldisc_sem){++++}, at: [<ffffffff8355cf92>] tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:284
 #1:  (&tty->atomic_write_lock){+.+.}, at: [<ffffffff8354be65>] tty_write_lock drivers/tty/tty_io.c:885 [inline]
 #1:  (&tty->atomic_write_lock){+.+.}, at: [<ffffffff8354be65>] tty_send_xchar+0x1b5/0x360 drivers/tty/tty_io.c:1086
 #2:  (&tty->termios_rwsem){++++}, at: [<ffffffff8354be98>] tty_send_xchar+0x1e8/0x360 drivers/tty/tty_io.c:1089
 #3:  (&(&port->lock)->rlock){-.-.}, at: [<ffffffff83560b1b>] tty_insert_flip_string_and_push_buffer+0x2b/0x160 drivers/tty/tty_buffer.c:569
 #4:  (console_lock){+.+.}, at: [<ffffffff81444378>] vprintk_func+0x58/0x160 kernel/printk/printk_safe.c:409

stack backtrace:
CPU: 1 PID: 7987 Comm: syz-executor406 Not tainted 4.14.305-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258
 check_prev_add kernel/locking/lockdep.c:1905 [inline]
 check_prevs_add kernel/locking/lockdep.c:2022 [inline]
 validate_chain kernel/locking/lockdep.c:2464 [inline]
 __lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491
 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
 console_lock_spinning_enable kernel/printk/printk.c:1590 [inline]
 console_unlock+0x36f/0xf20 kernel/printk/printk.c:2406
 vprintk_emit+0x224/0x620 kernel/printk/printk.c:1925
 vprintk_func+0x58/0x160 kernel/printk/printk_safe.c:409
 printk+0x9e/0xbc kernel/printk/printk.c:1998
 fail_dump lib/fault-inject.c:44 [inline]
 should_fail.cold+0xdf/0x149 lib/fault-inject.c:149
 should_failslab+0xd6/0x130 mm/failslab.c:32
 slab_pre_alloc_hook mm/slab.h:421 [inline]
 slab_alloc mm/slab.c:3376 [inline]
 __do_kmalloc mm/slab.c:3718 [inline]
 __kmalloc+0x6d/0x400 mm/slab.c:3729
 kmalloc include/linux/slab.h:493 [inline]
 tty_buffer_alloc+0xc0/0x270 drivers/tty/tty_buffer.c:169
 __tty_buffer_request_room+0x12c/0x290 drivers/tty/tty_buffer.c:268
 tty_insert_flip_string_fixed_flag+0x8b/0x210 drivers/tty/tty_buffer.c:313
 tty_insert_flip_string include/linux/tty_flip.h:36 [inline]
 tty_insert_flip_string_and_push_buffer+0x3e/0x160 drivers/tty/tty_buffer.c:570
 pty_write+0xc3/0xf0 drivers/tty/pty.c:118
 tty_send_xchar+0x245/0x360 drivers/tty/tty_io.c:1092
 n_tty_ioctl_helper+0x145/0x350 drivers/tty/tty_ioctl.c:926
 n_tty_ioctl+0x47/0x2e0 drivers/tty/n_tty.c:2466
 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:0x7f6d28001699
RSP: 002b:00007ffcb2860638 EFLAGS: 00000

Crashes (5335):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/02/16 08:28 linux-4.14.y a8ad60f2af58 6be0f1f5 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/02/12 00:29 linux-4.14.y a8ad60f2af58 93e26d60 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/25 13:20 linux-4.14.y 3949d1610004 9dfcf09c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/25 05:37 linux-4.14.y 3949d1610004 9dfcf09c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/22 23:31 linux-4.14.y 97205fccccdc cc0f9968 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/22 19:40 linux-4.14.y 97205fccccdc cc0f9968 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/22 18:56 linux-4.14.y 97205fccccdc cc0f9968 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/22 14:36 linux-4.14.y 97205fccccdc cc0f9968 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/21 17:39 linux-4.14.y 97205fccccdc cc0f9968 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/20 23:06 linux-4.14.y 97205fccccdc dd15ff29 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/20 07:05 linux-4.14.y 97205fccccdc 71197f3a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/13 08:04 linux-4.14.y c4215ee4771b 96166539 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/12 15:23 linux-4.14.y c4215ee4771b 96166539 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/12 15:05 linux-4.14.y c4215ee4771b 96166539 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/10 20:03 linux-4.14.y c4215ee4771b 48bc529a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/09 00:12 linux-4.14.y c4215ee4771b 1dac8c7a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/08 07:42 linux-4.14.y c4215ee4771b 1dac8c7a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/02 14:00 linux-4.14.y c4215ee4771b ab32d508 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/02 09:32 linux-4.14.y c4215ee4771b ab32d508 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/01 22:31 linux-4.14.y c4215ee4771b ab32d508 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/30 03:21 linux-4.14.y c4215ee4771b 44712fbc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/30 00:22 linux-4.14.y c4215ee4771b 44712fbc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/29 05:54 linux-4.14.y c4215ee4771b 44712fbc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/28 13:30 linux-4.14.y c4215ee4771b 44712fbc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/28 13:17 linux-4.14.y c4215ee4771b 44712fbc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/24 21:16 linux-4.14.y c4215ee4771b 9da18ae8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/23 19:48 linux-4.14.y c4215ee4771b 9da18ae8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/16 11:04 linux-4.14.y c4215ee4771b 6f9c033e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/16 08:11 linux-4.14.y c4215ee4771b 6f9c033e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/16 05:45 linux-4.14.y c4215ee4771b 6f9c033e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/16 03:09 linux-4.14.y c4215ee4771b 6f9c033e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/16 01:08 linux-4.14.y c4215ee4771b 6f9c033e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/13 00:37 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/11 04:08 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/11 01:02 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/10 16:39 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/10 06:39 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/08 11:01 linux-4.14.y 179ef7fe8677 d88f3abb .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/03 19:29 linux-4.14.y 179ef7fe8677 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/02 23:29 linux-4.14.y 179ef7fe8677 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/02 17:45 linux-4.14.y 179ef7fe8677 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/02 16:06 linux-4.14.y 179ef7fe8677 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2021/05/17 16:14 linux-4.14.y 7d7d1c0ab3eb a2eb125d .config console log report syz C ci2-linux-4-14 possible deadlock in console_unlock
2019/04/17 00:28 linux-4.14.y 1ec8f1f0bffe 505ab413 .config console log report syz C ci2-linux-4-14
2022/12/15 06:37 linux-4.14.y c4215ee4771b b18f0a64 .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/03/03 05:49 linux-4.14.y 7878a41b6cc1 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/29 23:38 linux-4.14.y 3949d1610004 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2023/01/28 18:38 linux-4.14.y 3949d1610004 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/17 16:55 linux-4.14.y c4215ee4771b 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/17 08:43 linux-4.14.y c4215ee4771b 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/12/11 12:33 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/11/05 17:28 linux-4.14.y a901bb6c7db7 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/11/04 14:48 linux-4.14.y a901bb6c7db7 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 possible deadlock in console_unlock
2022/10/22 16:52 linux-4.14.y 9d5c0b3a8e1a c0b80a55 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/10/19 12:48 linux-4.14.y 9d5c0b3a8e1a b31320fc .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/25 12:19 linux-4.14.y 4edbf74132a4 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/25 06:34 linux-4.14.y 4edbf74132a4 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/25 05:02 linux-4.14.y 4edbf74132a4 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/24 20:54 linux-4.14.y 4edbf74132a4 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/24 12:39 linux-4.14.y 4edbf74132a4 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/19 00:33 linux-4.14.y 5df8b4735177 dd9a85ff .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/17 06:01 linux-4.14.y 5df8b4735177 dd9a85ff .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/16 08:57 linux-4.14.y 5df8b4735177 dd9a85ff .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/16 00:06 linux-4.14.y 5df8b4735177 dd9a85ff .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in console_unlock
2022/09/12 06:31 linux-4.14.y 65640c873dcf 356d8217 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/09/11 17:58 linux-4.14.y 65640c873dcf 356d8217 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/09/10 20:56 linux-4.14.y 65640c873dcf 356d8217 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/08/31 05:28 linux-4.14.y e548869f356f 4a380809 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/08/19 16:34 linux-4.14.y b641242202ed 26a13b38 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/08/18 00:41 linux-4.14.y b641242202ed a9409d47 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/08/15 21:03 linux-4.14.y b641242202ed 8dfcaa3d .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/08/14 06:55 linux-4.14.y b641242202ed 8dfcaa3d .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/08/09 01:38 linux-4.14.y b641242202ed da700653 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/08/06 11:19 linux-4.14.y b641242202ed e853abd9 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/08/01 05:15 linux-4.14.y b641242202ed fef302b1 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/30 07:10 linux-4.14.y b641242202ed fef302b1 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/30 03:26 linux-4.14.y b641242202ed fef302b1 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/26 08:40 linux-4.14.y 9c3bf9cf362f 34795c51 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/23 07:05 linux-4.14.y 9c3bf9cf362f 22343af4 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/23 00:47 linux-4.14.y 9c3bf9cf362f 22343af4 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/21 02:05 linux-4.14.y 424a46ea058e 88cb1383 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/17 21:21 linux-4.14.y 424a46ea058e 95cb00d1 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/17 07:26 linux-4.14.y 424a46ea058e 95cb00d1 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/15 03:07 linux-4.14.y 424a46ea058e 5d921b08 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/14 19:53 linux-4.14.y 424a46ea058e 5d921b08 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/13 12:15 linux-4.14.y 424a46ea058e 5d921b08 .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/11 18:23 linux-4.14.y 1048779a1d7d f3f217ff .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2022/07/11 16:59 linux-4.14.y 1048779a1d7d f3f217ff .config console log report info ci2-linux-4-14 possible deadlock in console_unlock
2021/01/17 10:03 linux-4.14.y f79dc86058bc 813be542 .config console log report info ci2-linux-4-14
2019/04/16 04:12 linux-4.14.y 1ec8f1f0bffe 505ab413 .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.