syzbot


inconsistent lock state in valid_state (2)

Status: upstream: reported C repro on 2024/02/07 00:07
Subsystems: sound
[Documentation on labels]
Reported-by: syzbot+a225ee3df7e7f9372dbe@syzkaller.appspotmail.com
First crash: 78d, last: 57m
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: inconsistent lock state in sync_timeline_debug_remove (log)
Repro: C syz .config
  
Discussions (3)
Title Replies (including bot) Last reply
[syzbot] Monthly media report (Mar 2024) 0 (1) 2024/03/13 13:39
[syzbot] [dri?] [media?] inconsistent lock state in valid_state (2) 1 (4) 2024/02/27 11:16
[syzbot] Monthly media report (Feb 2024) 0 (1) 2024/02/12 10:24
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 inconsistent lock state in valid_state (2) C 60 11h04m 38d 0/3 upstream: reported C repro on 2024/03/13 18:08
upstream inconsistent lock state in valid_state kernel 1 423d 419d 0/26 auto-obsoleted due to no activity on 2023/06/23 05:39
linux-5.15 inconsistent lock state in valid_state 2 311d 390d 0/3 auto-obsoleted due to no activity on 2023/09/22 20:18
linux-6.1 inconsistent lock state in valid_state (2) origin:upstream missing-backport C done 166 2d22h 211d 0/3 upstream: reported C repro on 2023/09/22 23:56
linux-6.1 inconsistent lock state in valid_state 1 392d 392d 0/3 auto-obsoleted due to no activity on 2023/07/24 01:34
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/02/27 10:53 22m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master OK log

Sample crash report:
================================
WARNING: inconsistent lock state
6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted
--------------------------------
inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
syz-executor182/5056 [HC0[0]:SC0[0]:HE1:SE1] takes:
ffff8880296a5148 (&timer->lock){?...}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
ffff8880296a5148 (&timer->lock){?...}-{2:2}, at: class_spinlock_constructor include/linux/spinlock.h:561 [inline]
ffff8880296a5148 (&timer->lock){?...}-{2:2}, at: snd_timer_close_locked+0x53/0x8d0 sound/core/timer.c:412
{IN-HARDIRQ-W} state was registered at:
  lock_acquire+0x1e4/0x530 kernel/locking/lockdep.c:5754
  __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
  _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
  spin_lock include/linux/spinlock.h:351 [inline]
  class_spinlock_constructor include/linux/spinlock.h:561 [inline]
  snd_hrtimer_callback+0x54/0x370 sound/core/hrtimer.c:38
  __run_hrtimer kernel/time/hrtimer.c:1692 [inline]
  __hrtimer_run_queues+0x595/0xd00 kernel/time/hrtimer.c:1756
  hrtimer_interrupt+0x396/0x990 kernel/time/hrtimer.c:1818
  local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1032 [inline]
  __sysvec_apic_timer_interrupt+0x107/0x3a0 arch/x86/kernel/apic/apic.c:1049
  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]
  sysvec_apic_timer_interrupt+0xa1/0xc0 arch/x86/kernel/apic/apic.c:1043
  asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
  __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
  _raw_spin_unlock_irqrestore+0xd8/0x140 kernel/locking/spinlock.c:194
  spin_unlock_irqrestore include/linux/spinlock.h:406 [inline]
  unlock_page_lruvec_irqrestore include/linux/memcontrol.h:1672 [inline]
  folio_batch_move_lru+0x5bf/0x6e0 mm/swap.c:223
  lru_add_drain_cpu+0x10e/0x8c0 mm/swap.c:652
  lru_add_drain+0x123/0x3e0 mm/swap.c:752
  exit_mmap+0x28d/0xd40 mm/mmap.c:3282
  __mmput+0x115/0x3c0 kernel/fork.c:1345
  exit_mm+0x220/0x310 kernel/exit.c:569
  do_exit+0x99e/0x27e0 kernel/exit.c:865
  do_group_exit+0x207/0x2c0 kernel/exit.c:1027
  __do_sys_exit_group kernel/exit.c:1038 [inline]
  __se_sys_exit_group kernel/exit.c:1036 [inline]
  __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1036
  do_syscall_64+0xfb/0x240
  entry_SYSCALL_64_after_hwframe+0x6d/0x75
irq event stamp: 6199
hardirqs last  enabled at (6199): [<ffffffff8b765703>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
hardirqs last  enabled at (6199): [<ffffffff8b765703>] _raw_spin_unlock_irq+0x23/0x50 kernel/locking/spinlock.c:202
hardirqs last disabled at (6198): [<ffffffff8b76544d>] __raw_spin_lock_irq include/linux/spinlock_api_smp.h:117 [inline]
hardirqs last disabled at (6198): [<ffffffff8b76544d>] _raw_spin_lock_irq+0xad/0x120 kernel/locking/spinlock.c:170
softirqs last  enabled at (3644): [<ffffffff81597542>] invoke_softirq kernel/softirq.c:428 [inline]
softirqs last  enabled at (3644): [<ffffffff81597542>] __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633
softirqs last disabled at (3637): [<ffffffff81597542>] invoke_softirq kernel/softirq.c:428 [inline]
softirqs last disabled at (3637): [<ffffffff81597542>] __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&timer->lock);
  <Interrupt>
    lock(&timer->lock);

 *** DEADLOCK ***

3 locks held by syz-executor182/5056:
 #0: ffffffff8f2d3228 (register_mutex#4){+.+.}-{3:3}, at: odev_release+0x4e/0x80 sound/core/seq/oss/seq_oss.c:143
 #1: ffff88802da72978 (&q->timer_mutex){+.+.}-{3:3}, at: queue_delete sound/core/seq/seq_queue.c:124 [inline]
 #1: ffff88802da72978 (&q->timer_mutex){+.+.}-{3:3}, at: snd_seq_queue_delete+0x5b/0xf0 sound/core/seq/seq_queue.c:188
 #2: ffffffff8f2c1a68 (register_mutex){+.+.}-{3:3}, at: class_mutex_constructor include/linux/mutex.h:169 [inline]
 #2: ffffffff8f2c1a68 (register_mutex){+.+.}-{3:3}, at: snd_timer_close+0xa3/0x130 sound/core/timer.c:463

stack backtrace:
CPU: 1 PID: 5056 Comm: syz-executor182 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
 valid_state+0x13a/0x1c0 kernel/locking/lockdep.c:4013
 mark_lock_irq+0xbb/0xc20 kernel/locking/lockdep.c:4216
 mark_lock+0x223/0x350 kernel/locking/lockdep.c:4678
 mark_usage kernel/locking/lockdep.c:4587 [inline]
 __lock_acquire+0x112d/0x1fd0 kernel/locking/lockdep.c:5091
 lock_acquire+0x1e4/0x530 kernel/locking/lockdep.c:5754
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:351 [inline]
 class_spinlock_constructor include/linux/spinlock.h:561 [inline]
 snd_timer_close_locked+0x53/0x8d0 sound/core/timer.c:412
 snd_timer_close+0xae/0x130 sound/core/timer.c:464
 snd_seq_timer_close+0xa9/0xe0 sound/core/seq/seq_timer.c:302
 queue_delete sound/core/seq/seq_queue.c:126 [inline]
 snd_seq_queue_delete+0x8f/0xf0 sound/core/seq/seq_queue.c:188
 delete_seq_queue sound/core/seq/oss/seq_oss_init.c:371 [inline]
 snd_seq_oss_release+0x1d3/0x310 sound/core/seq/oss/seq_oss_init.c:416
 odev_release+0x56/0x80 sound/core/seq/oss/seq_oss.c:144
 __fput+0x429/0x8a0 fs/file_table.c:422
 task_work_run+0x24f/0x310 kernel/task_work.c:180
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xa1b/0x27e0 kernel/exit.c:878
 do_group_exit+0x207/0x2c0 kernel/exit.c:1027
 __do_sys_exit_group kernel/exit.c:1038 [inline]
 __se_sys_exit_group kernel/exit.c:1036 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1036
 do_syscall_64+0xfb/0x240
 entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7fea92af0c39
Code: Unable to access opcode bytes at 0x7fea92af0c0f.
RSP: 002b:00007ffc0f80eab8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fea92af0c39
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 

Crashes (56177):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/14 13:29 upstream fe46a7dd189e c8349e48 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/04/11 16:56 upstream fe46a7dd189e 478efa7f .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/04/11 16:08 upstream fe46a7dd189e 478efa7f .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/04/10 07:20 upstream fe46a7dd189e 56086b24 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/04/10 06:23 upstream fe46a7dd189e 56086b24 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/04/08 01:37 upstream fe46a7dd189e ca620dd8 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root inconsistent lock state in valid_state
2024/03/27 20:58 upstream 480e035fc4c7 454571b6 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/03/26 17:42 upstream fe46a7dd189e bcd9b39f .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/03/16 19:08 upstream 480e035fc4c7 d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/03/15 16:35 upstream fe46a7dd189e d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/03/15 06:07 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/03/15 05:34 upstream fe46a7dd189e d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/03/15 05:04 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/03/15 03:55 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/03/15 02:49 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/03/15 02:35 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs inconsistent lock state in valid_state
2024/03/15 02:02 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root inconsistent lock state in valid_state
2024/03/15 00:20 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root inconsistent lock state in valid_state
2024/03/14 23:52 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/02/27 00:56 upstream d206a76d7d27 edd6a5e9 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/04/16 06:05 net f99c5f563c17 0d592ce4 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce inconsistent lock state in valid_state
2024/04/15 03:25 bpf 443574b03387 c8349e48 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/03/31 16:33 net f99c5f563c17 6baf5069 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce inconsistent lock state in valid_state
2024/03/31 03:07 bpf 443574b03387 6baf5069 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/02 18:53 bpf-next 14bb1e8c8d4a 6baf5069 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce inconsistent lock state in valid_state
2024/03/31 11:25 bpf-next 14bb1e8c8d4a 6baf5069 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce inconsistent lock state in valid_state
2024/04/17 19:24 net f99c5f563c17 bd38b692 .config console log report syz [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce inconsistent lock state in valid_state
2024/04/15 23:32 bpf 443574b03387 0d592ce4 .config strace log report syz [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/13 16:34 net f99c5f563c17 c8349e48 .config strace log report syz [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce inconsistent lock state in valid_state
2024/04/12 21:49 bpf 443574b03387 27de0a5c .config console log report syz [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/20 21:38 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/04/20 18:31 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root inconsistent lock state in valid_state
2024/04/20 17:28 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/04/20 16:04 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/04/20 13:45 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/04/20 06:10 upstream dbe0a7be2838 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/04/20 04:51 upstream 3cdb45594619 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/04/20 03:03 upstream 3cdb45594619 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root inconsistent lock state in valid_state
2024/04/19 20:22 upstream 3cdb45594619 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root inconsistent lock state in valid_state
2024/04/19 19:47 upstream dbe0a7be2838 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/02/02 13:57 upstream 021533194476 60bf9982 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce inconsistent lock state in valid_state
2024/04/15 18:20 upstream fe46a7dd189e c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 inconsistent lock state in valid_state
2024/04/21 06:12 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/21 04:15 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/21 02:31 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/21 01:08 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/20 21:54 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/20 14:53 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/20 09:17 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/20 07:48 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/20 05:04 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/19 22:04 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/19 18:15 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/19 10:27 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/19 08:39 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/19 06:32 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/19 04:50 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/18 20:58 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/18 19:32 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/18 17:59 bpf 443574b03387 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/18 03:38 net f99c5f563c17 bd38b692 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce inconsistent lock state in valid_state
2024/04/18 02:34 bpf 443574b03387 bd38b692 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/18 00:47 bpf 443574b03387 bd38b692 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/17 18:35 bpf 443574b03387 bd38b692 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/17 13:18 bpf 443574b03387 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/17 12:12 bpf 443574b03387 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/17 09:20 bpf 443574b03387 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/17 08:00 bpf 443574b03387 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce inconsistent lock state in valid_state
2024/04/20 20:25 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/20 12:22 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/20 11:12 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/19 15:40 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/19 13:55 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/19 03:26 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/18 14:47 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/18 11:55 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/18 09:46 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/18 08:44 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/18 06:01 linux-next 4eab35893071 bd38b692 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
2024/04/17 16:28 linux-next 4eab35893071 bd38b692 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root inconsistent lock state in valid_state
* Struck through repros no longer work on HEAD.