syzbot


inconsistent lock state in valid_state (2)

Status: upstream: reported C repro on 2023/09/22 23:56
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+3c3cf70f154b5131a759@syzkaller.appspotmail.com
First crash: 222d, last: 2h23m
Fix commit to backport (bisect log) :
tree: upstream
commit 013ff63b649475f0ee134e2c8d0c8e65284ede50
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Jun 30 12:17:02 2023 +0000

  fs/ntfs3: Add more attributes checks in mi_enum_attr()

  
Fix bisection: the issue occurs on the latest tested release (bisect log)
Crash: KASAN: out-of-bounds Write in end_buffer_read_sync (log)
Repro: C syz .config
  
Bug presence (3)
Date Name Commit Repro Result
2023/11/07 linux-6.1.y (ToT) 4a61839152cc C [report] inconsistent lock state in valid_state
2023/09/23 upstream (ToT) d90b0276af8f C [report] kernel panic: stack is corrupted in __lock_acquire
2023/11/07 upstream (ToT) be3ca57cfb77 C Didn't crash
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) origin:upstream C 138 2h02m 50d 0/3 upstream: reported C repro on 2024/03/13 18:08
upstream inconsistent lock state in valid_state kernel 1 434d 430d 0/26 auto-obsoleted due to no activity on 2023/06/23 05:39
linux-5.15 inconsistent lock state in valid_state 2 322d 402d 0/3 auto-obsoleted due to no activity on 2023/09/22 20:18
upstream inconsistent lock state in valid_state (2) sound C inconclusive 56840 28m 85d 0/26 upstream: reported C repro on 2024/02/07 00:07
linux-6.1 inconsistent lock state in valid_state 1 403d 403d 0/3 auto-obsoleted due to no activity on 2023/07/24 01:34
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2023/11/10 01:10 7h32m fix candidate upstream job log (1)
2023/10/27 17:35 2h42m bisect fix linux-6.1.y job log (0) log

Sample crash report:
================================
WARNING: inconsistent lock state
6.1.89-syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
syz-executor411/3719 [HC0[0]:SC1[1]:HE0:SE0] takes:
ffff8880b9935e90 (lock#9){+.?.}-{2:2}, at: local_lock_acquire include/linux/local_lock_internal.h:29 [inline]
ffff8880b9935e90 (lock#9){+.?.}-{2:2}, at: __mmap_lock_do_trace_acquire_returned+0x84/0x670 mm/mmap_lock.c:237
{SOFTIRQ-ON-W} state was registered at:
  lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
  local_lock_acquire include/linux/local_lock_internal.h:29 [inline]
  __mmap_lock_do_trace_acquire_returned+0x9d/0x670 mm/mmap_lock.c:237
  __mmap_lock_trace_acquire_returned include/linux/mmap_lock.h:36 [inline]
  mmap_read_trylock include/linux/mmap_lock.h:137 [inline]
  get_mmap_lock_carefully mm/memory.c:5304 [inline]
  lock_mm_and_find_vma+0x219/0x2e0 mm/memory.c:5366
  do_user_addr_fault arch/x86/mm/fault.c:1343 [inline]
  handle_page_fault arch/x86/mm/fault.c:1462 [inline]
  exc_page_fault+0x169/0x660 arch/x86/mm/fault.c:1518
  asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
irq event stamp: 285
hardirqs last  enabled at (284): [<ffffffff8a94eb6f>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:159 [inline]
hardirqs last  enabled at (284): [<ffffffff8a94eb6f>] _raw_spin_unlock_irq+0x1f/0x40 kernel/locking/spinlock.c:202
hardirqs last disabled at (285): [<ffffffff815960b6>] queue_work_on+0xf6/0x250 kernel/workqueue.c:1545
softirqs last  enabled at (0): [<ffffffff8151c7c1>] rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
softirqs last  enabled at (0): [<ffffffff8151c7c1>] rcu_read_lock include/linux/rcupdate.h:791 [inline]
softirqs last  enabled at (0): [<ffffffff8151c7c1>] copy_process+0x9e1/0x4060 kernel/fork.c:2132
softirqs last disabled at (281): [<ffffffff81542035>] invoke_softirq kernel/softirq.c:445 [inline]
softirqs last disabled at (281): [<ffffffff81542035>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:650

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

       CPU0
       ----
  lock(lock#9);
  <Interrupt>
    lock(lock#9);

 *** DEADLOCK ***

8 locks held by syz-executor411/3719:
 #0: ffff88807e1288d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
 #0: ffff88807e1288d8 (&mm->mmap_lock){++++}-{3:3}, at: get_mmap_lock_carefully mm/memory.c:5304 [inline]
 #0: ffff88807e1288d8 (&mm->mmap_lock){++++}-{3:3}, at: lock_mm_and_find_vma+0x2e/0x2e0 mm/memory.c:5366
 #1: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 #1: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
 #1: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: filemap_map_pages+0x277/0x12c0 mm/filemap.c:3415
 #2: ffff888021c99c78 (ptlock_ptr(page)#2){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
 #2: ffff888021c99c78 (ptlock_ptr(page)#2){+.+.}-{2:2}, at: filemap_map_pages+0x958/0x12c0 mm/filemap.c:3426
 #3: ffffc900001e0bc0 ((&sdp->delay_work)){+.-.}-{0:0}, at: call_timer_fn+0xc2/0x6b0 kernel/time/timer.c:1501
 #4: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 #4: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
 #4: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: __queue_work+0xe5/0xf90 kernel/workqueue.c:1443
 #5: ffff8880b983a258 (&pool->lock){-.-.}-{2:2}, at: __queue_work+0x58c/0xf90
 #6: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 #6: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
 #6: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: __bpf_trace_run kernel/trace/bpf_trace.c:2272 [inline]
 #6: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: bpf_trace_run3+0x146/0x440 kernel/trace/bpf_trace.c:2313
 #7: ffff88807e1288d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
 #7: ffff88807e1288d8 (&mm->mmap_lock){++++}-{3:3}, at: stack_map_get_build_id_offset+0x232/0x9c0 kernel/bpf/stackmap.c:144

stack backtrace:
CPU: 1 PID: 3719 Comm: syz-executor411 Not tainted 6.1.89-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 valid_state+0x136/0x1c0 kernel/locking/lockdep.c:3969
 mark_lock_irq+0xa8/0xba0 kernel/locking/lockdep.c:4172
 mark_lock+0x21c/0x340 kernel/locking/lockdep.c:4628
 __lock_acquire+0xb7f/0x1f80 kernel/locking/lockdep.c:5003
 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
 local_lock_acquire include/linux/local_lock_internal.h:29 [inline]
 __mmap_lock_do_trace_acquire_returned+0x9d/0x670 mm/mmap_lock.c:237
 __mmap_lock_trace_acquire_returned include/linux/mmap_lock.h:36 [inline]
 mmap_read_trylock include/linux/mmap_lock.h:137 [inline]
 stack_map_get_build_id_offset+0x99e/0x9c0 kernel/bpf/stackmap.c:144
 __bpf_get_stack+0x495/0x570 kernel/bpf/stackmap.c:452
 ____bpf_get_stack_raw_tp kernel/trace/bpf_trace.c:1877 [inline]
 bpf_get_stack_raw_tp+0x1b2/0x220 kernel/trace/bpf_trace.c:1867
 bpf_prog_e6cf5f9c69743609+0x3a/0x3e
 bpf_dispatcher_nop_func include/linux/bpf.h:989 [inline]
 __bpf_prog_run include/linux/filter.h:603 [inline]
 bpf_prog_run include/linux/filter.h:610 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:2273 [inline]
 bpf_trace_run3+0x231/0x440 kernel/trace/bpf_trace.c:2313
 __traceiter_workqueue_queue_work+0x79/0xd0 include/trace/events/workqueue.h:23
 trace_workqueue_queue_work include/trace/events/workqueue.h:23 [inline]
 __queue_work+0xeeb/0xf90 kernel/workqueue.c:1500
 queue_work_on+0x14b/0x250 kernel/workqueue.c:1548
 call_timer_fn+0x1ad/0x6b0 kernel/time/timer.c:1504
 expire_timers kernel/time/timer.c:1549 [inline]
 __run_timers+0x67c/0x890 kernel/time/timer.c:1820
 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1833
 __do_softirq+0x2e9/0xa4c kernel/softirq.c:571
 invoke_softirq kernel/softirq.c:445 [inline]
 __irq_exit_rcu+0x155/0x240 kernel/softirq.c:650
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:662
 sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1106
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:constant_test_bit arch/x86/include/asm/bitops.h:207 [inline]
RIP: 0010:arch_test_bit arch/x86/include/asm/bitops.h:239 [inline]
RIP: 0010:_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]
RIP: 0010:PageSwapBacked include/linux/page-flags.h:502 [inline]
RIP: 0010:mm_counter_file+0xd5/0x2c0 include/linux/mm.h:2125
Code: 83 e6 01 31 ff e8 ab 57 bd ff 48 89 d8 48 83 e0 01 75 5f 0f 1f 44 00 00 e8 b8 53 bd ff 4c 89 f7 be 08 00 00 00 e8 7b cc 14 00 <4c> 89 f0 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 d5 ca 14 00
RSP: 0000:ffffc90003aff988 EFLAGS: 00000256
RAX: ffffffff81cd3b01 RBX: ffffea0001c32e88 RCX: ffffffff81cd3bb5
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffea0001c32ec0
RBP: ffffc90003affa90 R08: dffffc0000000000 R09: fffff940003865d9
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffffd40003865d9 R14: ffffea0001c32ec0 R15: ffffea0001c32ec8
 do_set_pte+0x2fe/0x590 mm/memory.c:4404
 filemap_map_pages+0xc7c/0x12c0 mm/filemap.c:3452
 do_fault_around mm/memory.c:4581 [inline]
 do_read_fault mm/memory.c:4607 [inline]
 do_fault mm/memory.c:4741 [inline]
 handle_pte_fault mm/memory.c:5013 [inline]
 __handle_mm_fault mm/memory.c:5155 [inline]
 handle_mm_fault+0x33e2/0x5340 mm/memory.c:5276
 do_user_addr_fault arch/x86/mm/fault.c:1371 [inline]
 handle_page_fault arch/x86/mm/fault.c:1462 [inline]
 exc_page_fault+0x26f/0x660 arch/x86/mm/fault.c:1518
 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7fb1275148e0
Code: e9 75 e6 ff ff e8 90 be fe ff ba 01 00 00 00 e9 d9 f2 ff ff b8 01 00 00 00 e9 8f e7 ff ff ba 01 00 00 00 e9 a9 ee ff ff 66 90 <41> 57 41 56 41 55 49 89 d5 41 54 55 53 48 89 fb 48 81 ec 18 05 00
RSP: 002b:00007ffda18dfe48 EFLAGS: 00010206
RAX: 00007ffda18e0000 RBX: 00007ffda18e0000 RCX: 0000000000000000
RDX: 00007ffda18dffe8 RSI: 00007fb12754801d RDI: 00007ffda18dfe60
RBP: 00007ffda18dff50 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb12754801d
R13: 00007ffda18dffe8 R14: 0000000000000000 R15: 00007ffda18dfe60
 </TASK>
----------------
Code disassembly (best guess):
   0:	83 e6 01             	and    $0x1,%esi
   3:	31 ff                	xor    %edi,%edi
   5:	e8 ab 57 bd ff       	call   0xffbd57b5
   a:	48 89 d8             	mov    %rbx,%rax
   d:	48 83 e0 01          	and    $0x1,%rax
  11:	75 5f                	jne    0x72
  13:	0f 1f 44 00 00       	nopl   0x0(%rax,%rax,1)
  18:	e8 b8 53 bd ff       	call   0xffbd53d5
  1d:	4c 89 f7             	mov    %r14,%rdi
  20:	be 08 00 00 00       	mov    $0x8,%esi
  25:	e8 7b cc 14 00       	call   0x14cca5
* 2a:	4c 89 f0             	mov    %r14,%rax <-- trapping instruction
  2d:	48 c1 e8 03          	shr    $0x3,%rax
  31:	42 80 3c 20 00       	cmpb   $0x0,(%rax,%r12,1)
  36:	74 08                	je     0x40
  38:	4c 89 f7             	mov    %r14,%rdi
  3b:	e8 d5 ca 14 00       	call   0x14cb15

Crashes (207):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/30 03:01 linux-6.1.y dcbc050cb0d3 f10afd69 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/13 08:03 linux-6.1.y bf1e3b1cb1e0 c8349e48 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/13 07:18 linux-6.1.y bf1e3b1cb1e0 c8349e48 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/03/31 02:03 linux-6.1.y e5cd595e23c1 6baf5069 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2023/09/22 23:56 linux-6.1.y a356197db198 0b6a67ac .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/21 23:00 linux-6.1.y 6741e066ec76 af24b050 .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/15 06:11 linux-6.1.y cd5d98c0556c c8349e48 .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/11 04:34 linux-6.1.y bf1e3b1cb1e0 33b9e058 .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/05/02 16:16 linux-6.1.y 909ba1f1b414 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/05/02 03:28 linux-6.1.y dcbc050cb0d3 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/05/01 01:00 linux-6.1.y dcbc050cb0d3 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/30 23:58 linux-6.1.y dcbc050cb0d3 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/30 16:02 linux-6.1.y dcbc050cb0d3 3ce4924c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/30 13:59 linux-6.1.y dcbc050cb0d3 3ce4924c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/30 12:54 linux-6.1.y dcbc050cb0d3 3ce4924c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/29 23:02 linux-6.1.y dcbc050cb0d3 f10afd69 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/29 20:59 linux-6.1.y dcbc050cb0d3 f10afd69 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/29 12:16 linux-6.1.y dcbc050cb0d3 27e33c58 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/29 10:18 linux-6.1.y f2295faba5e8 27e33c58 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/29 08:44 linux-6.1.y f2295faba5e8 27e33c58 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/29 08:44 linux-6.1.y f2295faba5e8 27e33c58 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/28 23:03 linux-6.1.y f2295faba5e8 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/28 14:25 linux-6.1.y f2295faba5e8 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/27 20:46 linux-6.1.y f2295faba5e8 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/27 16:32 linux-6.1.y f2295faba5e8 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/27 10:00 linux-6.1.y 6741e066ec76 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/25 16:11 linux-6.1.y 6741e066ec76 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/25 06:43 linux-6.1.y 6741e066ec76 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/23 23:51 linux-6.1.y 6741e066ec76 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/23 11:47 linux-6.1.y 6741e066ec76 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/18 08:48 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/17 18:38 linux-6.1.y 6741e066ec76 acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/17 15:57 linux-6.1.y 6741e066ec76 acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/17 15:16 linux-6.1.y 6741e066ec76 acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/17 12:05 linux-6.1.y 6741e066ec76 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/17 10:46 linux-6.1.y 6741e066ec76 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/16 19:29 linux-6.1.y cd5d98c0556c 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/16 18:25 linux-6.1.y cd5d98c0556c 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/16 16:31 linux-6.1.y cd5d98c0556c 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/16 12:37 linux-6.1.y cd5d98c0556c 0d592ce4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/16 11:10 linux-6.1.y cd5d98c0556c 0d592ce4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/16 06:07 linux-6.1.y cd5d98c0556c 0d592ce4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/16 03:32 linux-6.1.y cd5d98c0556c 0d592ce4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/15 18:49 linux-6.1.y cd5d98c0556c b9af7e61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/15 18:42 linux-6.1.y cd5d98c0556c b9af7e61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/15 17:28 linux-6.1.y cd5d98c0556c b9af7e61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/15 16:23 linux-6.1.y cd5d98c0556c b9af7e61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/15 13:14 linux-6.1.y cd5d98c0556c b9af7e61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/15 08:53 linux-6.1.y cd5d98c0556c c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/15 04:48 linux-6.1.y cd5d98c0556c c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/15 01:35 linux-6.1.y cd5d98c0556c c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/04/14 23:52 linux-6.1.y cd5d98c0556c c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
2024/04/14 21:15 linux-6.1.y cd5d98c0556c c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
* Struck through repros no longer work on HEAD.