syzbot


possible deadlock in console_unlock (2)

Status: fixed on 2023/02/24 13:51
Subsystems: serial
[Documentation on labels]
Reported-by: syzbot+0b7c8bfd17c00d016fb4@syzkaller.appspotmail.com
Fix commit: 09c5ba0aa2fc printk: add kthread console printers
First crash: 869d, last: 414d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: fixed by (bisect log) :
commit faebd693c59387b7b765fab64b543855e15a91b4
Author: John Ogness <john.ogness@linutronix.de>
Date: Thu Apr 21 21:22:36 2022 +0000

  printk: rename cpulock functions

  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] possible deadlock in console_unlock (2) 3 (5) 2022/06/27 07:42
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in console_unlock C done 22098 869d 2122d 26/26 closed as dup on 2021/01/21 05:31
linux-4.19 possible deadlock in console_unlock C 5771 391d 1813d 0/1 upstream: reported C repro on 2019/04/11 15:05
linux-4.14 possible deadlock in console_unlock C 5335 391d 1808d 0/1 upstream: reported C repro on 2019/04/16 05:13
android-414 possible deadlock in console_unlock C 5 1848d 1812d 0/1 public: reported C repro on 2019/04/12 00:01

Sample crash report:
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 1
======================================================
WARNING: possible circular locking dependency detected
5.18.0-syzkaller-01850-gaa051d36ce4a #0 Not tainted
------------------------------------------------------
syz-executor354/3608 is trying to acquire lock:
ffffffff8bc92f80 (console_owner){....}-{0:0}, at: console_unlock+0x35e/0xdd0 kernel/printk/printk.c:2770

but task is already holding lock:
ffff888011b7e958 (&port->lock){-...}-{2:2}, at: pty_write+0xea/0x1e0 drivers/tty/pty.c:120

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&port->lock){-...}-{2:2}:
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0x39/0x50 kernel/locking/spinlock.c:162
       tty_port_tty_get+0x1f/0x100 drivers/tty/tty_port.c:306
       tty_port_default_wakeup+0x11/0x40 drivers/tty/tty_port.c:48
       serial8250_tx_chars+0x4f3/0xa50 drivers/tty/serial/8250/8250_port.c:1866
       serial8250_handle_irq.part.0+0x328/0x3d0 drivers/tty/serial/8250/8250_port.c:1953
       serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1926 [inline]
       serial8250_default_handle_irq+0xb2/0x220 drivers/tty/serial/8250/8250_port.c:1970
       serial8250_interrupt+0xfd/0x200 drivers/tty/serial/8250/8250_core.c:126
       __handle_irq_event_percpu+0x22b/0x880 kernel/irq/handle.c:158
       handle_irq_event_percpu kernel/irq/handle.c:193 [inline]
       handle_irq_event+0xa7/0x1e0 kernel/irq/handle.c:210
       handle_edge_irq+0x25f/0xd00 kernel/irq/chip.c:817
       generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
       handle_irq arch/x86/kernel/irq.c:231 [inline]
       __common_interrupt+0x9d/0x210 arch/x86/kernel/irq.c:250
       common_interrupt+0xa4/0xc0 arch/x86/kernel/irq.c:240
       asm_common_interrupt+0x27/0x40 arch/x86/include/asm/idtentry.h:640
       native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
       arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
       acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
       acpi_idle_do_entry+0x1c6/0x250 drivers/acpi/processor_idle.c:554
       acpi_idle_enter+0x369/0x510 drivers/acpi/processor_idle.c:691
       cpuidle_enter_state+0x1b1/0xc80 drivers/cpuidle/cpuidle.c:237
       cpuidle_enter+0x4a/0xa0 drivers/cpuidle/cpuidle.c:351
       call_cpuidle kernel/sched/idle.c:155 [inline]
       cpuidle_idle_call kernel/sched/idle.c:236 [inline]
       do_idle+0x3e8/0x590 kernel/sched/idle.c:303
       cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:400
       rest_init+0x169/0x270 init/main.c:726
       arch_call_rest_init+0xf/0x14 init/main.c:882
       start_kernel+0x46e/0x48f init/main.c:1137
       secondary_startup_64_no_verify+0xce/0xdb

-> #1 (&port_lock_key){-...}-{2:2}:
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0x39/0x50 kernel/locking/spinlock.c:162
       serial8250_console_write+0x9cb/0xc30 drivers/tty/serial/8250/8250_port.c:3358
       call_console_drivers kernel/printk/printk.c:1952 [inline]
       console_unlock+0x9bc/0xdd0 kernel/printk/printk.c:2774
       vprintk_emit+0x1b4/0x5f0 kernel/printk/printk.c:2272
       vprintk+0x80/0x90 kernel/printk/printk_safe.c:50
       _printk+0xba/0xed kernel/printk/printk.c:2293
       register_console kernel/printk/printk.c:3131 [inline]
       register_console+0x410/0x7c0 kernel/printk/printk.c:3012
       univ8250_console_init+0x3a/0x46 drivers/tty/serial/8250/8250_core.c:679
       console_init+0x3c1/0x58d kernel/printk/printk.c:3231
       start_kernel+0x2fa/0x48f init/main.c:1065
       secondary_startup_64_no_verify+0xce/0xdb

-> #0 (console_owner){....}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3064 [inline]
       check_prevs_add kernel/locking/lockdep.c:3183 [inline]
       validate_chain kernel/locking/lockdep.c:3798 [inline]
       __lock_acquire+0x2ac6/0x56c0 kernel/locking/lockdep.c:5022
       lock_acquire kernel/locking/lockdep.c:5634 [inline]
       lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5599
       console_lock_spinning_enable kernel/printk/printk.c:1794 [inline]
       console_unlock+0x3b1/0xdd0 kernel/printk/printk.c:2771
       vprintk_emit+0x1b4/0x5f0 kernel/printk/printk.c:2272
       vprintk+0x80/0x90 kernel/printk/printk_safe.c:50
       _printk+0xba/0xed kernel/printk/printk.c:2293
       fail_dump lib/fault-inject.c:45 [inline]
       should_fail+0x472/0x5a0 lib/fault-inject.c:146
       should_failslab+0x5/0x10 mm/slab_common.c:1313
       slab_pre_alloc_hook mm/slab.h:724 [inline]
       slab_alloc_node mm/slub.c:3131 [inline]
       slab_alloc mm/slub.c:3225 [inline]
       __kmalloc+0x7e/0x350 mm/slub.c:4410
       kmalloc include/linux/slab.h:586 [inline]
       tty_buffer_alloc+0x23f/0x2a0 drivers/tty/tty_buffer.c:178
       __tty_buffer_request_room+0x156/0x2a0 drivers/tty/tty_buffer.c:274
       tty_insert_flip_string_fixed_flag+0x8c/0x240 drivers/tty/tty_buffer.c:321
       tty_insert_flip_string include/linux/tty_flip.h:41 [inline]
       pty_write+0x11c/0x1e0 drivers/tty/pty.c:122
       n_tty_write+0xa7a/0xfc0 drivers/tty/n_tty.c:2271
       do_tty_write drivers/tty/tty_io.c:1024 [inline]
       file_tty_write.constprop.0+0x520/0x900 drivers/tty/tty_io.c:1095
       call_write_iter include/linux/fs.h:2052 [inline]
       new_sync_write+0x38a/0x560 fs/read_write.c:504
       vfs_write+0x7c0/0xac0 fs/read_write.c:591
       ksys_write+0x127/0x250 fs/read_write.c:644
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x46/0xb0

other info that might help us debug this:

Chain exists of:
  console_owner --> &port_lock_key --> &port->lock

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

6 locks held by syz-executor354/3608:
 #0: ffff88807dfa3098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffff88807dfa3130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:950 [inline]
 #1: ffff88807dfa3130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:973 [inline]
 #1: ffff88807dfa3130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write.constprop.0+0x299/0x900 drivers/tty/tty_io.c:1095
 #2: ffff88807dfa32e8 (&tty->termios_rwsem){++++}-{3:3}, at: n_tty_write+0x1bf/0xfc0 drivers/tty/n_tty.c:2231
 #3: ffffc900013da378 (&ldata->output_lock){+.+.}-{3:3}, at: n_tty_write+0xa47/0xfc0 drivers/tty/n_tty.c:2270
 #4: ffff888011b7e958 (&port->lock){-...}-{2:2}, at: pty_write+0xea/0x1e0 drivers/tty/pty.c:120
 #5: ffffffff8bd733c0 (console_lock){+.+.}-{0:0}, at: vprintk+0x80/0x90 kernel/printk/printk_safe.c:50

stack backtrace:
CPU: 1 PID: 3608 Comm: syz-executor354 Not tainted 5.18.0-syzkaller-01850-gaa051d36ce4a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2144
 check_prev_add kernel/locking/lockdep.c:3064 [inline]
 check_prevs_add kernel/locking/lockdep.c:3183 [inline]
 validate_chain kernel/locking/lockdep.c:3798 [inline]
 __lock_acquire+0x2ac6/0x56c0 kernel/locking/lockdep.c:5022
 lock_acquire kernel/locking/lockdep.c:5634 [inline]
 lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5599
 console_lock_spinning_enable kernel/printk/printk.c:1794 [inline]
 console_unlock+0x3b1/0xdd0 kernel/printk/printk.c:2771
 vprintk_emit+0x1b4/0x5f0 kernel/printk/printk.c:2272
 vprintk+0x80/0x90 kernel/printk/printk_safe.c:50
 _printk+0xba/0xed kernel/printk/printk.c:2293
 fail_dump lib/fault-inject.c:45 [inline]
 should_fail+0x472/0x5a0 lib/fault-inject.c:146
 should_failslab+0x5/0x10 mm/slab_common.c:1313
 slab_pre_alloc_hook mm/slab.h:724 [inline]
 slab_alloc_node mm/slub.c:3131 [inline]
 slab_alloc mm/slub.c:3225 [inline]
 __kmalloc+0x7e/0x350 mm/slub.c:4410
 kmalloc include/linux/slab.h:586 [inline]
 tty_buffer_alloc+0x23f/0x2a0 drivers/tty/tty_buffer.c:178
 __tty_buffer_request_room+0x156/0x2a0 drivers/tty/tty_buffer.c:274
 tty_insert_flip_string_fixed_flag+0x8c/0x240 drivers/tty/tty_buffer.c:321
 tty_insert_flip_string include/linux/tty_flip.h:41 [inline]
 pty_write+0x11c/0x1e0 drivers/tty/pty.c:122
 n_tty_write+0xa7a/0xfc0 drivers/tty/n_tty.c:2271
 do_tty_write drivers/tty/tty_io.c:1024 [inline]
 file_tty_write.constprop.0+0x520/0x900 drivers/tty/tty_io.c:1095
 call_write_iter include/linux/fs.h:2052 [inline]
 new_sync_write+0x38a/0x560 fs/read_write.c:504
 vfs_write+0x7c0/0xac0 fs/read_write.c:591
 ksys_write+0x127/0x250 fs/read_write.c:644
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x46/0xb0
RIP: 0033:0x7f9917a46669
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff90698ff8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f9917a46669
RDX: 000000000000ff2e RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 00007fff90699000 R08: 0000000000000001 R09: 00007f9917a00033
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
CPU: 1 PID: 3608 Comm: syz-executor354 Not tainted 5.18.0-syzkaller-01850-gaa051d36ce4a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 fail_dump lib/fault-inject.c:52 [inline]
 should_fail.cold+0x5/0xa lib/fault-inject.c:146
 should_failslab+0x5/0x10 mm/slab_common.c:1313
 slab_pre_alloc_hook mm/slab.h:724 [inline]
 slab_alloc_node mm/slub.c:3131 [inline]
 slab_alloc mm/slub.c:3225 [inline]
 __kmalloc+0x7e/0x350 mm/slub.c:4410
 kmalloc include/linux/slab.h:586 [inline]
 tty_buffer_alloc+0x23f/0x2a0 drivers/tty/tty_buffer.c:178
 __tty_buffer_request_room+0x156/0x2a0 drivers/tty/tty_buffer.c:274
 tty_insert_flip_string_fixed_flag+0x8c/0x240 drivers/tty/tty_buffer.c:321
 tty_insert_flip_string include/linux/tty_flip.h:41 [inline]
 pty_write+0x11c/0x1e0 drivers/tty/pty.c:122
 n_tty_write+0xa7a/0xfc0 drivers/tty/n_tty.c:2271
 do_tty_write drivers/tty/tty_io.c:1024 [inline]
 file_tty_write.constprop.0+0x520/0x900 drivers/tty/tty_io.c:1095
 call_write_iter include/linux/fs.h:2052 [inline]
 new_sync_write+0x38a/0x560 fs/read_write.c:504
 vfs_write+0x7c0/0xac0 fs/read_write.c:591
 ksys_write+0x127/0x250 fs/read_write.c:644
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x46/0xb0
RIP: 0033:0x7f9917a46669
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff90698ff8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f9917a46669
RDX: 000000000000ff2e RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 00007fff90699000 R08: 0000000000000001 R09: 00007f9917a00033
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Crashes (599):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/05/25 08:28 upstream aa051d36ce4a 647c0e27 .config strace log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/22 18:26 upstream eaea45fc0e7b 7268fa62 .config strace log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/20 09:18 upstream b015dcd62b86 cb1ac2e7 .config strace log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/16 02:50 upstream bc403203d65a 744a39e2 .config strace log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/16 02:18 upstream bc403203d65a 744a39e2 .config strace log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/16 01:58 upstream bc403203d65a 744a39e2 .config strace log report syz C ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/15 09:49 upstream 2fe1020d73ca 744a39e2 .config strace log report syz C ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/13 02:07 upstream 0ac824f379fb 9ad6612a .config strace log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/12 23:13 upstream 0ac824f379fb 9ad6612a .config strace log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/10 04:21 upstream 9be9ed2612b5 8b277b8e .config strace log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/04/30 01:49 upstream 2d0de93ca251 44a5ca63 .config console log report syz C ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/23 22:10 upstream 13bc32bad705 131df97d .config console log report syz C ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/23 15:41 upstream c00c5e1d157b 131df97d .config console log report syz C ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/22 20:47 upstream d569e86915b7 131df97d .config console log report syz C ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/07 01:16 upstream 3e732ebf7316 97582466 .config console log report syz C ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/01/24 16:40 upstream dd81e1c7d5fb 214351e1 .config console log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/01/24 13:01 upstream dd81e1c7d5fb 214351e1 .config console log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/01/06 05:54 upstream 49ef78e59b07 6acc789a .config console log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/01/06 02:17 upstream 49ef78e59b07 6acc789a .config console log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/01/04 09:55 upstream c9e6606c7fe9 7f723fbe .config console log report syz C ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/22 23:04 upstream eaea45fc0e7b 7268fa62 .config console log report syz C ci-upstream-kasan-gce-386 possible deadlock in console_unlock
2022/05/15 23:06 upstream bc403203d65a 744a39e2 .config console log report syz C ci-upstream-kasan-gce-386 possible deadlock in console_unlock
2022/05/11 09:36 upstream feb9c5e19e91 8d7b3b67 .config console log report syz C ci-upstream-kasan-gce-386 possible deadlock in console_unlock
2022/01/24 14:55 upstream dd81e1c7d5fb 214351e1 .config console log report syz C ci-upstream-kasan-gce-386 possible deadlock in console_unlock
2021/11/13 20:33 linux-next f2e19fd15bd7 83f5c9b5 .config console log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in console_unlock
2022/05/25 11:09 upstream aa051d36ce4a 647c0e27 .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/24 08:31 upstream 1e57930e9f40 e7f9308d .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/24 03:36 upstream 1e57930e9f40 e7f9308d .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/23 16:16 upstream 4b0986a3613c 4c7657cb .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/23 08:23 upstream 4b0986a3613c 7268fa62 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/23 00:26 upstream eaea45fc0e7b 7268fa62 .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/22 22:25 upstream eaea45fc0e7b 7268fa62 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/21 11:57 upstream 3b5e1590a267 7268fa62 .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/21 02:00 upstream 3d7285a335ed bd37ad7e .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/20 22:41 upstream 3d7285a335ed bd37ad7e .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/18 10:29 upstream 210e04ff7681 744a39e2 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/18 08:08 upstream 210e04ff7681 744a39e2 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/05/17 12:16 upstream 42226c989789 744a39e2 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/05/17 07:14 upstream 42226c989789 744a39e2 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/16 18:48 upstream 42226c989789 744a39e2 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/05/16 14:39 upstream 42226c989789 744a39e2 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/16 01:54 upstream bc403203d65a 744a39e2 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/05/16 00:49 upstream bc403203d65a 744a39e2 .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/05/13 15:09 upstream f3f19f939c11 107f6434 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/05/12 12:09 upstream feb9c5e19e91 beb0b407 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/11 18:17 upstream feb9c5e19e91 beb0b407 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/05/11 13:21 upstream feb9c5e19e91 8d7b3b67 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/05/11 11:01 upstream feb9c5e19e91 8d7b3b67 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/05/02 12:43 upstream 672c0c517342 2df221f6 .config console log report info ci-qemu-upstream possible deadlock in console_unlock
2022/04/29 16:30 upstream 38d741cb70b3 44a5ca63 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/29 02:22 upstream 259b897e5a79 e9076525 .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/04/28 18:04 upstream 8f4dd16603ce e9076525 .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/28 02:43 upstream 8f4dd16603ce 8a1f1f07 .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/04/27 08:16 upstream cf424ef014ac 1fa34c1b .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/04/26 09:55 upstream d615b5416f8a 1fa34c1b .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/04/25 02:38 upstream 5206548f6e67 131df97d .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/24 20:12 upstream 22da5264abf4 131df97d .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/24 17:01 upstream 22da5264abf4 131df97d .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/04/24 15:33 upstream 22da5264abf4 131df97d .config console log report info ci-upstream-kasan-gce possible deadlock in console_unlock
2022/04/24 03:15 upstream 13bc32bad705 131df97d .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2022/04/23 20:15 upstream c00c5e1d157b 131df97d .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in console_unlock
2022/04/23 08:21 upstream c00c5e1d157b 131df97d .config console log report info ci-upstream-kasan-gce-root possible deadlock in console_unlock
2021/11/10 09:08 upstream cb690f5238d7 55fa030c .config console log report info ci-qemu-upstream possible deadlock in console_unlock
2022/04/26 06:39 upstream d615b5416f8a 152baedd .config console log report info ci-upstream-kasan-gce-386 possible deadlock in console_unlock
2022/04/22 09:56 upstream 59f0c2447e25 2738b391 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in console_unlock
2022/04/11 01:47 upstream 1862a69c9174 e22c3da3 .config console log report info ci-qemu-upstream-386 possible deadlock in console_unlock
2022/04/25 04:09 linux-next f1244c81da13 131df97d .config console log report info ci-upstream-linux-next-kasan-gce-root possible deadlock in console_unlock
2023/02/08 01:38 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d 15c3d445 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2023/02/05 19:07 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d be607b78 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2023/02/05 01:41 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d be607b78 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/12/31 03:04 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d ab32d508 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/12/20 18:25 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d 4791c8e9 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/11/27 01:37 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d f4470a7b .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/10/31 08:30 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d 2a71366b .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/10/20 08:56 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d b31320fc .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/10/13 17:21 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d e3cf86a1 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/08/27 01:02 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d e5a303f1 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/08/20 04:40 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d 26a13b38 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/08/17 17:00 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d 4e72d229 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/08/04 00:13 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d 1c9013ac .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/07/24 08:10 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d 22343af4 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
2022/07/16 12:41 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 0966d385830d 95cb00d1 .config console log report info ci-qemu2-riscv64 possible deadlock in console_unlock
* Struck through repros no longer work on HEAD.