syzbot


inconsistent lock state in valid_state (2)

Status: upstream: reported C repro on 2024/03/13 18:08
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+db6a6f32b60f325125ab@syzkaller.appspotmail.com
First crash: 275d, last: 58d
Fix commit to backport (bisect log) :
tree: upstream
commit 7d6be67cfdd4a53cea7147313ca13c531e3a470f
Author: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: Fri Jun 21 01:08:41 2024 +0000

  mm: mmap_lock: replace get_memcg_path_buf() with on-stack buffer

  
Bug presence (1)
Date Name Commit Repro Result
2024/11/07 upstream (ToT) ff7afaeca1a1 C Didn't crash
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream inconsistent lock state in valid_state kernel 1 660d 656d 0/28 auto-obsoleted due to no activity on 2023/06/23 05:39
upstream inconsistent lock state in valid_state (4) ppp C 69 37d 117d 0/28 upstream: reported C repro on 2024/08/19 05:03
linux-5.15 inconsistent lock state in valid_state 2 548d 627d 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 334 58d 448d 0/3 upstream: reported C repro on 2023/09/22 23:56
upstream inconsistent lock state in valid_state (2) sound C inconclusive 57405 187d 311d 25/28 fixed on 2024/06/11 03:41
upstream inconsistent lock state in valid_state (3) mm C error 376 134d 183d 27/28 fixed on 2024/08/14 03:44
linux-6.1 inconsistent lock state in valid_state 1 629d 629d 0/3 auto-obsoleted due to no activity on 2023/07/24 01:34
Last patch testing requests (4)
Created Duration User Patch Repo Result
2024/11/02 12:34 17m retest repro linux-5.15.y OK log
2024/11/02 12:34 20m retest repro linux-5.15.y OK log
2024/11/02 12:34 14m retest repro linux-5.15.y log
2024/11/01 20:06 15m retest repro linux-5.15.y OK log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/08/10 12:19 4h38m fix candidate upstream OK (1) job log

Sample crash report:
================================
WARNING: inconsistent lock state
5.15.152-syzkaller #0 Not tainted
--------------------------------
inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
syz-executor908/3501 [HC0[0]:SC1[1]:HE0:SE0] takes:
ffff8880b9b28098 (&base->lock){?.-.}-{2:2}, at: lock_timer_base+0x120/0x260 kernel/time/timer.c:946
{IN-HARDIRQ-W} state was registered at:
  lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
  __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
  _raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
  lock_timer_base+0x120/0x260 kernel/time/timer.c:946
  add_timer_on+0x1eb/0x580 kernel/time/timer.c:1169
  handle_irq_event_percpu kernel/irq/handle.c:198 [inline]
  handle_irq_event+0x124/0x2b0 kernel/irq/handle.c:213
  handle_level_irq+0x3ab/0x6c0 kernel/irq/chip.c:653
  generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
  handle_irq arch/x86/kernel/irq.c:231 [inline]
  __common_interrupt+0xd7/0x1f0 arch/x86/kernel/irq.c:250
  common_interrupt+0x9f/0xc0 arch/x86/kernel/irq.c:240
  asm_common_interrupt+0x22/0x40 arch/x86/include/asm/idtentry.h:629
  __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:161 [inline]
  _raw_spin_unlock_irqrestore+0xd4/0x130 kernel/locking/spinlock.c:194
  __setup_irq+0x1302/0x1d90 kernel/irq/manage.c:1817
  request_threaded_irq+0x2a7/0x380 kernel/irq/manage.c:2206
  request_irq include/linux/interrupt.h:168 [inline]
  setup_default_timer_irq+0x1f/0x30 arch/x86/kernel/time.c:70
  x86_late_time_init+0x51/0x86 arch/x86/kernel/time.c:94
  start_kernel+0x40a/0x535 init/main.c:1100
  secondary_startup_64_no_verify+0xb1/0xbb
irq event stamp: 1001
hardirqs last  enabled at (1000): [<ffffffff8a25468f>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:168 [inline]
hardirqs last  enabled at (1000): [<ffffffff8a25468f>] _raw_spin_unlock_irq+0x1f/0x40 kernel/locking/spinlock.c:202
hardirqs last disabled at (1001): [<ffffffff8a25433c>] __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:108 [inline]
hardirqs last disabled at (1001): [<ffffffff8a25433c>] _raw_spin_lock_irqsave+0xac/0x120 kernel/locking/spinlock.c:162
softirqs last  enabled at (962): [<ffffffff818e10fd>] spin_unlock_bh include/linux/spinlock.h:408 [inline]
softirqs last  enabled at (962): [<ffffffff818e10fd>] bpf_link_settle+0x7d/0x140 kernel/bpf/syscall.c:2590
softirqs last disabled at (997): [<ffffffff814d64f5>] invoke_softirq kernel/softirq.c:432 [inline]
softirqs last disabled at (997): [<ffffffff814d64f5>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:637

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

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

 *** DEADLOCK ***

6 locks held by syz-executor908/3501:
 #0: ffff88801997b928
 (&mm->mmap_lock
){++++}-{3:3}
, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
, at: do_user_addr_fault arch/x86/mm/fault.c:1338 [inline]
, at: handle_page_fault arch/x86/mm/fault.c:1485 [inline]
, at: exc_page_fault+0x181/0x740 arch/x86/mm/fault.c:1541
 #1: ffffffff8c91f720
 (rcu_read_lock
){....}-{1:2}
, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:268
 #2: ffffc90000dd0be0
 ((&dsp_spl_tl)
){+.-.}-{0:0}
, at: lockdep_copy_map include/linux/lockdep.h:45 [inline]
, at: call_timer_fn+0xbe/0x560 kernel/time/timer.c:1411
 #3: ffffffff8d798d18
 (dsp_lock
){+.-.}-{2:2}, at: dsp_cmx_send+0x22/0x2240 drivers/isdn/mISDN/dsp_cmx.c:1643
 #4: ffff8880b9b28098
 (&base->lock
){?.-.}-{2:2}
, at: lock_timer_base+0x120/0x260 kernel/time/timer.c:946
 #5: ffffffff8c91f720
 (rcu_read_lock
){....}-{1:2}
, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:268

stack backtrace:
CPU: 1 PID: 3501 Comm: syz-executor908 Not tainted 5.15.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 valid_state+0x134/0x1c0 kernel/locking/lockdep.c:3932
 mark_lock_irq+0xa8/0xba0 kernel/locking/lockdep.c:4135
 mark_lock+0x21a/0x340 kernel/locking/lockdep.c:4591
 mark_held_locks kernel/locking/lockdep.c:4193 [inline]
 __trace_hardirqs_on_caller kernel/locking/lockdep.c:4211 [inline]
 lockdep_hardirqs_on_prepare+0x27d/0x7a0 kernel/locking/lockdep.c:4278
 trace_hardirqs_on+0x67/0x80 kernel/trace/trace_preemptirq.c:49
 __local_bh_enable_ip+0x164/0x1f0 kernel/softirq.c:388
 sock_hash_delete_elem+0x1a0/0x2f0 net/core/sock_map.c:945
 bpf_prog_6f5f05285f674219+0x3a/0xf28
 bpf_dispatcher_nop_func include/linux/bpf.h:780 [inline]
 __bpf_prog_run include/linux/filter.h:625 [inline]
 bpf_prog_run include/linux/filter.h:632 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:1880 [inline]
 bpf_trace_run3+0x1d1/0x380 kernel/trace/bpf_trace.c:1918
 trace_timer_start include/trace/events/timer.h:52 [inline]
 enqueue_timer+0x3ae/0x540 kernel/time/timer.c:586
 internal_add_timer kernel/time/timer.c:611 [inline]
 __mod_timer+0xa60/0xeb0 kernel/time/timer.c:1062
 dsp_cmx_send+0x21bb/0x2240 drivers/isdn/mISDN/dsp_cmx.c:1850
 call_timer_fn+0x16d/0x560 kernel/time/timer.c:1421
 expire_timers kernel/time/timer.c:1466 [inline]
 __run_timers+0x67c/0x890 kernel/time/timer.c:1737
 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1750
 __do_softirq+0x3b3/0x93a kernel/softirq.c:558
 invoke_softirq kernel/softirq.c:432 [inline]
 __irq_exit_rcu+0x155/0x240 kernel/softirq.c:637
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:649
 sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1096
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:check_preemption_disabled+0x19/0x110 lib/smp_processor_id.c:14
Code: cc 48 c7 c7 a0 8e d8 8a 48 c7 c6 e0 8e d8 8a eb 00 41 57 41 56 41 54 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 <65> 8b 1d 68 38 e6 75 65 8b 05 d1 92 e6 75 a9 ff ff ff 7f 74 22 65
RSP: 0000:ffffc900011dfad8 EFLAGS: 00000286
RAX: 0a87c466efc75300 RBX: 0000000000000000 RCX: ffff888078b7bb80
RDX: ffff888078b7bb80 RSI: ffffffff8ad88ee0 RDI: ffffffff8ad88ea0
RBP: ffffc900011dfc10 R08: ffffffff81b8dde7 R09: fffffbfff1f79e19
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000014
R13: dffffc0000000000 R14: 1ffff9200023bf6c R15: ffff888078b7bb80
 rcu_dynticks_curr_cpu_in_eqs kernel/rcu/tree.c:331 [inline]
 rcu_is_watching+0x11/0xa0 kernel/rcu/tree.c:1123
 rcu_read_lock_held_common kernel/rcu/update.c:108 [inline]
 rcu_read_lock_held+0x11/0x40 kernel/rcu/update.c:309
 count_memcg_event_mm+0x145/0x3e0 include/linux/memcontrol.h:1079
 handle_mm_fault+0x161/0x5950 mm/memory.c:4834
 do_user_addr_fault arch/x86/mm/fault.c:1397 [inline]
 handle_page_fault arch/x86/mm/fault.c:1485 [inline]
 exc_page_fault+0x271/0x740 arch/x86/mm/fault.c:1541
 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0033:0x7f0ac813e178
Code: Unable to access opcode bytes at RIP 0x7f0ac813e14e.
RSP: 002b:00007ffc688f8628 EFLAGS: 00010206
RAX: 00007f0ac816ead8 RBX: 0000000000000000 RCX: 0000000000000004
RDX: 00007f0ac816fd00 RSI: 0000000000000000 RDI: 00007f0ac816ead8
RBP: 00007f0ac816d118 R08: 0000000000000006 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f0ac816fce8
R13: 0000000000000000 R14: 00007f0ac816fd00 R15: 00007f0ac80c5160
 </TASK>
------------[ cut here ]------------
raw_local_irq_restore() called with IRQs enabled
WARNING: CPU: 1 PID: 3501 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10
Modules linked in:

CPU: 1 PID: 3501 Comm: syz-executor908 Not tainted 5.15.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10
Code: 24 48 c7 c7 a0 d1 89 8a e8 6c d1 fe ff 80 3d ae 7f b4 03 00 74 01 c3 c6 05 a4 7f b4 03 01 48 c7 c7 80 0c 8b 8a e8 f3 1b 30 f7 <0f> 0b c3 41 56 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00 48 89 44
RSP: 0000:ffffc90000dd0898 EFLAGS: 00010246

RAX: 0a87c466efc75300 RBX: 1ffff920001ba118 RCX: ffff888078b7bb80
RDX: 0000000000000103 RSI: 0000000000000103 RDI: 0000000000000000
RBP: ffffc90000dd0930 R08: ffffffff8166665c R09: fffffbfff1922849
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff920001ba114 R14: ffffc90000dd08c0 R15: 0000000000000046
FS:  0000555555e3c380(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0ac813e14e CR3: 000000001a390000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <IRQ>
 __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
 _raw_spin_unlock_irqrestore+0x118/0x130 kernel/locking/spinlock.c:194
 __mod_timer+0xa8e/0xeb0 kernel/time/timer.c:1065
----------------
Code disassembly (best guess):
   0:	cc                   	int3
   1:	48 c7 c7 a0 8e d8 8a 	mov    $0xffffffff8ad88ea0,%rdi
   8:	48 c7 c6 e0 8e d8 8a 	mov    $0xffffffff8ad88ee0,%rsi
   f:	eb 00                	jmp    0x11
  11:	41 57                	push   %r15
  13:	41 56                	push   %r14
  15:	41 54                	push   %r12
  17:	53                   	push   %rbx
  18:	48 83 ec 10          	sub    $0x10,%rsp
  1c:	65 48 8b 04 25 28 00 	mov    %gs:0x28,%rax
  23:	00 00
  25:	48 89 44 24 08       	mov    %rax,0x8(%rsp)
* 2a:	65 8b 1d 68 38 e6 75 	mov    %gs:0x75e63868(%rip),%ebx        # 0x75e63899 <-- trapping instruction
  31:	65 8b 05 d1 92 e6 75 	mov    %gs:0x75e692d1(%rip),%eax        # 0x75e69309
  38:	a9 ff ff ff 7f       	test   $0x7fffffff,%eax
  3d:	74 22                	je     0x61
  3f:	65                   	gs

Crashes (208):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/03/26 16:34 linux-5.15.y b95c01af2113 bcd9b39f .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/10/17 10:47 linux-5.15.y 3a5928702e71 666f77ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/10/17 09:04 linux-5.15.y 3a5928702e71 666f77ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/10/17 09:01 linux-5.15.y 3a5928702e71 666f77ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/10/15 15:44 linux-5.15.y 3a5928702e71 7eb57b4a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/10/09 19:00 linux-5.15.y 3a5928702e71 56fb2cb7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/10/05 16:48 linux-5.15.y 3a5928702e71 d7906eff .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/10/05 13:39 linux-5.15.y 3a5928702e71 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/09/28 07:47 linux-5.15.y 3a5928702e71 440b26ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/09/27 17:03 linux-5.15.y 3a5928702e71 9314348a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/09/26 21:51 linux-5.15.y 3a5928702e71 9314348a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/09/26 05:12 linux-5.15.y 3a5928702e71 0d19f247 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/09/26 02:13 linux-5.15.y 3a5928702e71 0d19f247 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/09/25 13:54 linux-5.15.y 3a5928702e71 349a68c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/08/19 01:20 linux-5.15.y 7e89efd3ae1c dbc93b08 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/08/10 04:35 linux-5.15.y 7e89efd3ae1c 6f4edef4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/08/07 16:04 linux-5.15.y 7e89efd3ae1c 109d2082 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/08/05 15:43 linux-5.15.y 7e89efd3ae1c e35c337f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/07/28 11:43 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/07/23 02:36 linux-5.15.y 7c6d66f0266f 708c10c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/07/19 13:13 linux-5.15.y 7c6d66f0266f ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/07/19 04:06 linux-5.15.y 7c6d66f0266f ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/07/17 03:11 linux-5.15.y f45bea23c39c 215bec2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/07/14 21:44 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/06/21 19:08 linux-5.15.y 4878aadf2d15 edc5149a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/06/16 09:14 linux-5.15.y c61bd26ae81a f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/06/15 04:54 linux-5.15.y c61bd26ae81a f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/06/14 23:25 linux-5.15.y c61bd26ae81a f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/06/11 09:24 linux-5.15.y c61bd26ae81a b7d9eb04 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/06/05 13:47 linux-5.15.y c61bd26ae81a 5aa1a7c9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/06/03 14:11 linux-5.15.y c61bd26ae81a 0aba2352 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/23 09:40 linux-5.15.y 83655231580b 4c2072ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/05/18 03:37 linux-5.15.y 83655231580b c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/17 16:44 linux-5.15.y 83655231580b a12e99e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/17 14:22 linux-5.15.y 83655231580b a12e99e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/16 21:32 linux-5.15.y 284087d4f7d5 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/16 03:53 linux-5.15.y 284087d4f7d5 ef5d53ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/15 11:06 linux-5.15.y 284087d4f7d5 94b087b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/14 20:03 linux-5.15.y 284087d4f7d5 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/14 02:19 linux-5.15.y 284087d4f7d5 fdb4c10c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/13 11:27 linux-5.15.y 284087d4f7d5 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/09 09:19 linux-5.15.y 284087d4f7d5 05079661 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/08 18:52 linux-5.15.y 284087d4f7d5 20bf80e1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/04 03:17 linux-5.15.y 284087d4f7d5 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/04 01:45 linux-5.15.y 284087d4f7d5 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/05/03 10:13 linux-5.15.y 284087d4f7d5 dd26401e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2024/04/30 14:07 linux-5.15.y b925f60c6ee7 3ce4924c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/04/13 07:59 linux-5.15.y cdfd0a7f0139 c8349e48 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/03/29 02:46 linux-5.15.y 9465fef4ae35 e91187ee .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in valid_state
2024/03/13 18:07 linux-5.15.y 574362648507 f919f202 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
* Struck through repros no longer work on HEAD.