syzbot


possible deadlock in pty_write

Status: upstream: reported C repro on 2020/02/03 21:58
Reported-by: syzbot+3118a33395397bb6b0ca@syzkaller.appspotmail.com
First crash: 886d, last: 45d

Cause bisection: introduced by (bisect log) :
commit 65b27995a4ab8fc51b4adc6b4dcdca20f7a595bb
Author: Heiner Kallweit <hkallweit1@gmail.com>
Date: Mon Aug 12 21:52:19 2019 +0000

  net: phy: let phy_speed_down/up support speeds >1Gbps

Crash: general protection fault in batadv_iv_ogm_queue_add (log)
Repro: C syz .config

Fix bisection: the fix commit could be any of (bisect log):
  ccaaaf6fe5a5 Merge tag 'mpx-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/daveh/x86-mpx
  4d7620341eda Merge tag 'kbuild-fixes-v5.13' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild
similar bugs (2):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 possible deadlock in pty_write C 208 28d 886d 0/1 upstream: reported C repro on 2020/02/01 01:19
linux-4.19 possible deadlock in pty_write C error 151 11d 885d 0/1 upstream: reported C repro on 2020/02/02 11:26
Patch testing requests:
Created Duration User Patch Repo Result
2020/10/11 14:02 10m rkovhaev@gmail.com upstream report log
2020/09/10 20:07 10m rkovhaev@gmail.com git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git stable report log
2020/09/08 14:55 10m rkovhaev@gmail.com git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 205d300aea75 report log
2020/08/22 16:07 10m rkovhaev@gmail.com upstream report log

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-rc7-syzkaller-00119-gb015dcd62b86 #0 Not tainted
------------------------------------------------------
syz-executor190/3606 is trying to acquire lock:
ffffffff8bc8dc00 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1874 [inline]
ffffffff8bc8dc00 (console_owner){....}-{0:0}, at: vprintk_emit+0x316/0x5f0 kernel/printk/printk.c:2271

but task is already holding lock:
ffff88801fd9d958 (&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+0x1e/0x40 arch/x86/include/asm/idtentry.h:636
       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:110 [inline]
       acpi_idle_do_entry+0x1c6/0x250 drivers/acpi/processor_idle.c:551
       acpi_idle_enter+0x361/0x500 drivers/acpi/processor_idle.c:686
       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+0x47f/0x4a0 init/main.c:1140
       secondary_startup_64_no_verify+0xc3/0xcb

-> #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+0x30b/0x4a0 init/main.c:1068
       secondary_startup_64_no_verify+0xc3/0xcb

-> #0 (console_owner){....}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3065 [inline]
       check_prevs_add kernel/locking/lockdep.c:3188 [inline]
       validate_chain kernel/locking/lockdep.c:3803 [inline]
       __lock_acquire+0x2ac6/0x56c0 kernel/locking/lockdep.c:5029
       lock_acquire kernel/locking/lockdep.c:5641 [inline]
       lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5606
       console_trylock_spinning kernel/printk/printk.c:1895 [inline]
       vprintk_emit+0x353/0x5f0 kernel/printk/printk.c:2271
       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 mm/slab.c:3299 [inline]
       __do_kmalloc mm/slab.c:3708 [inline]
       __kmalloc+0x7b/0x4d0 mm/slab.c:3719
       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:2050 [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+0x44/0xae

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 ***

5 locks held by syz-executor190/3606:
 #0: ffff88801fd9c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffff88801fd9c130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:950 [inline]
 #1: ffff88801fd9c130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:973 [inline]
 #1: ffff88801fd9c130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write.constprop.0+0x299/0x900 drivers/tty/tty_io.c:1095
 #2: ffff88801fd9c2e8 (&tty->termios_rwsem){++++}-{3:3}, at: n_tty_write+0x1bf/0xfc0 drivers/tty/n_tty.c:2231
 #3: ffffc900013ec378 (&ldata->output_lock){+.+.}-{3:3}, at: n_tty_write+0xa47/0xfc0 drivers/tty/n_tty.c:2270
 #4: ffff88801fd9d958 (&port->lock){-.-.}-{2:2}, at: pty_write+0xea/0x1e0 drivers/tty/pty.c:120

stack backtrace:
CPU: 1 PID: 3606 Comm: syz-executor190 Not tainted 5.18.0-rc7-syzkaller-00119-gb015dcd62b86 #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:2145
 check_prev_add kernel/locking/lockdep.c:3065 [inline]
 check_prevs_add kernel/locking/lockdep.c:3188 [inline]
 validate_chain kernel/locking/lockdep.c:3803 [inline]
 __lock_acquire+0x2ac6/0x56c0 kernel/locking/lockdep.c:5029
 lock_acquire kernel/locking/lockdep.c:5641 [inline]
 lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5606
 console_trylock_spinning kernel/printk/printk.c:1895 [inline]
 vprintk_emit+0x353/0x5f0 kernel/printk/printk.c:2271
 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 mm/slab.c:3299 [inline]
 __do_kmalloc mm/slab.c:3708 [inline]
 __kmalloc+0x7b/0x4d0 mm/slab.c:3719
 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:2050 [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+0x44/0xae
RIP: 0033:0x7ff74838b229
Code: 28 c3 e8 aa 15 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcf4f58338 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007ff74838b229
RDX: 0000000000000060 RSI: 0000000020000380 RDI: 0000000000000003
RBP: 00007ffcf4f58350 R08: 0000000000000001 R09: 00007ffcf4f5833d
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ff74840ee10 R14: 00007ffcf4f583a8 R15: 0000000000000000
 </TASK>
CPU: 1 PID: 3606 Comm: syz-executor190 Not tainted 5.18.0-rc7-syzkaller-00119-gb015dcd62b86 #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 mm/slab.c:3299 [inline]
 __do_kmalloc mm/slab.c:3708 [inline]
 __kmalloc+0x7b/0x4d0 mm/slab.c:3719
 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:2050 [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+0x44/0xae
RIP: 0033:0x7ff74838b229
Code: 28 c3 e8 aa 15 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcf4f58338 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007ff74838b229
RDX: 0000000000000060 RSI: 0000000020000380 RDI: 0000000000000003
RBP: 00007ffcf4f58350 R08: 0000000000000001 R09: 00007ffcf4f5833d
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 00007ff74840ee10 R14: 00007ffcf4f583a8 R15: 0000000000000000
 </TASK>

Crashes (192):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-selinux-root 2022/05/20 08:31 upstream b015dcd62b86 cb1ac2e7 .config log report syz C possible deadlock in pty_write
ci-upstream-kasan-gce-root 2020/02/01 03:01 upstream ccaaaf6fe5a5 c30117b2 .config log report syz C
ci-upstream-kasan-gce-selinux-root 2022/05/22 15:48 upstream eaea45fc0e7b 7268fa62 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/05/22 02:54 upstream 6c3f5bec9b40 7268fa62 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/05/21 01:49 upstream 3d7285a335ed bd37ad7e .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-selinux-root 2022/05/20 08:15 upstream b015dcd62b86 cb1ac2e7 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/05/16 01:43 upstream bc403203d65a 744a39e2 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/05/15 09:37 upstream 2fe1020d73ca 744a39e2 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-selinux-root 2022/04/27 17:44 upstream 46cf2c613f4b 1fa34c1b .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-selinux-root 2022/04/25 14:25 upstream af2d861d4cd2 c889aef9 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-selinux-root 2022/04/20 18:19 upstream 559089e0a93d 160a3f31 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-selinux-root 2022/04/20 06:53 upstream 559089e0a93d 7d7bc738 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/04/09 05:59 upstream 6c7376da2358 e22c3da3 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/04/07 00:44 upstream 3e732ebf7316 97582466 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/03/18 01:52 upstream 551acdc3c3d2 e2d91b1d .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/03/11 06:18 upstream dda64ead7e82 9e8eaa75 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-selinux-root 2022/03/08 01:14 upstream ea4424be1688 7bdd8b2c .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/03/05 03:04 upstream 07ebd38a0da2 45a13a73 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/02/28 04:45 upstream 52a025546731 45a13a73 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-selinux-root 2022/02/27 20:47 upstream 2293be58d6a1 45a13a73 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-selinux-root 2022/02/22 10:20 upstream 038101e6b2cd 6e821dbf .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/02/22 09:03 upstream 038101e6b2cd 6e821dbf .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/02/21 03:57 upstream 7f25f0412c9e 3cd800e4 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/02/16 19:01 upstream c5d9ae265b10 8b9ca619 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/02/11 01:34 upstream e3c85076d7a6 0b33604d .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/02/07 06:32 upstream d8ad2ce873ab a7dab638 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/02/06 15:32 upstream 90c9e950c0de a7dab638 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/02/06 05:48 upstream 90c9e950c0de a7dab638 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/01/31 11:21 upstream 26291c54e111 6b7c57fe .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/01/31 00:44 upstream 24f4db1f3a27 495e00c5 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/01/27 15:19 upstream 626b2dda7651 2cbffd88 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/01/27 09:20 upstream 0280e3c58f92 2cbffd88 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/01/24 03:15 upstream dd81e1c7d5fb 214351e1 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/01/19 01:27 upstream 99613159ad74 731a2d23 .config log report info possible deadlock in pty_write
ci-qemu-upstream 2022/01/18 03:12 upstream 0c947b893d69 731a2d23 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/01/16 15:19 upstream d0a231f01e5b 723cfaf0 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce 2022/01/14 14:23 upstream fb3b0673b7d5 b8d780ab .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/01/13 02:46 upstream f079ab01b560 44d1319a .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/01/12 01:37 upstream 6f38be8f2ccd 44d1319a .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2022/01/07 06:16 upstream b2b436ec0205 6acc789a .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-386 2022/04/23 03:40 upstream d569e86915b7 131df97d .config log report info possible deadlock in pty_write
ci-qemu-upstream-386 2022/04/16 09:21 upstream 59250f8a7f3a 8bcc32a6 .config log report info possible deadlock in pty_write
ci-qemu-upstream-386 2022/03/02 00:12 upstream 575115360652 45a13a73 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-386 2022/02/09 16:46 upstream e6251ab4551f 0b33604d .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-386 2022/02/07 10:27 upstream d8ad2ce873ab a7dab638 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-386 2022/01/30 23:32 upstream 24f4db1f3a27 495e00c5 .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-386 2022/01/14 00:02 upstream 455e73a07f6e b8d780ab .config log report info possible deadlock in pty_write
ci-upstream-linux-next-kasan-gce-root 2022/04/17 07:08 linux-next 40354149f4d7 8bcc32a6 .config log report info possible deadlock in pty_write
ci-upstream-linux-next-kasan-gce-root 2022/03/05 06:32 linux-next 91265a6da44d 45a13a73 .config log report info possible deadlock in pty_write
ci-upstream-linux-next-kasan-gce-root 2022/01/13 17:55 linux-next 27c9d5b3c24a 44d1319a .config log report info possible deadlock in pty_write
ci-upstream-kasan-gce-root 2020/02/01 01:26 upstream ccaaaf6fe5a5 c30117b2 .config log report
ci-qemu-upstream-386 2020/10/10 04:45 upstream 8a5f78d98c26 93817d89 .config log report info