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: 1057d, last: 16h19m
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()

[report pending]
  
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 (13)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 inconsistent lock state in valid_state (2) missing-backport 4 syz, C done 208 667d 885d 0/3 auto-obsoleted due to no activity on 2024/12/26 10:49
linux-6.6 inconsistent lock state in valid_state (2) 4 43 4d01h 10d 0/2 upstream: reported on 2026/08/05 10:00
linux-6.6 inconsistent lock state in valid_state origin:upstream 4 syz, C done 19 79d 119d 2/2 fixed on 2026/06/29 10:59
upstream inconsistent lock state in valid_state (7) prio:high x25 4 syz 284 7h18m 4d23h 0/29 upstream: reported syz repro on 2026/08/11 00:12
linux-5.15 inconsistent lock state in valid_state (3) origin:upstream 4 syz, C done 165 2h20m 117d 2/3 upstream: reported C repro on 2026/04/20 22:51
upstream inconsistent lock state in valid_state (6) kernfs comedi 4 2 301d 300d 0/29 auto-obsoleted due to no activity on 2026/01/26 19:03
upstream inconsistent lock state in valid_state kernel 4 1 1269d 1265d 0/29 auto-obsoleted due to no activity on 2023/06/23 05:39
upstream inconsistent lock state in valid_state (4) linux1394 ppp 4 syz, C error 72 551d 726d 0/29 auto-obsoleted due to no activity on 2025/04/21 16:31
linux-5.15 inconsistent lock state in valid_state 4 2 1158d 1237d 0/3 auto-obsoleted due to no activity on 2023/09/22 20:18
upstream inconsistent lock state in valid_state (5) net 4 515 346d 350d 0/29 closed as invalid on 2025/09/16 17:45
upstream inconsistent lock state in valid_state (2) sound 4 syz, C inconclusive 57405 796d 920d 25/29 fixed on 2024/06/11 03:41
upstream inconsistent lock state in valid_state (3) mm 4 syz, C error 376 743d 792d 27/29 fixed on 2024/08/14 03:44
linux-6.1 inconsistent lock state in valid_state 4 1 1238d 1238d 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 OK (1) job log
2023/10/27 17:35 2h42m bisect fix linux-6.1.y OK (0) job log log

Sample crash report:
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
swapper/0/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff8880791f8648 ((work_completion)(&(&host->detect)->work)){+.?.}-{0:0}, at: __flush_work+0x109/0xac0 kernel/workqueue.c:3072
{SOFTIRQ-ON-W} state was registered at:
  lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
  __flush_work+0x122/0xac0 kernel/workqueue.c:3072
  __cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3163
  __mmc_stop_host drivers/mmc/core/core.c:2303 [inline]
  mmc_stop_host+0xd5/0x460 drivers/mmc/core/core.c:2308
  mmc_remove_host+0x11/0x60 drivers/mmc/core/host.c:651
  vub300_disconnect+0x14b/0x2e0 drivers/mmc/host/vub300.c:2382
  usb_unbind_interface+0x203/0x870 drivers/usb/core/driver.c:458
  device_remove drivers/base/dd.c:549 [inline]
  __device_release_driver drivers/base/dd.c:1279 [inline]
  device_release_driver_internal+0x4cf/0x7c0 drivers/base/dd.c:1305
  bus_remove_device+0x2dd/0x400 drivers/base/bus.c:531
  device_del+0x63f/0xa80 drivers/base/core.c:3900
  usb_disable_device+0x3e7/0x8a0 drivers/usb/core/message.c:1472
  usb_disconnect+0x33c/0x8a0 drivers/usb/core/hub.c:2314
  hub_port_connect drivers/usb/core/hub.c:5361 [inline]
  hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
  port_event drivers/usb/core/hub.c:5817 [inline]
  hub_event+0x1d27/0x5200 drivers/usb/core/hub.c:5899
  process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
  process_scheduled_works kernel/workqueue.c:2355 [inline]
  worker_thread+0xd6e/0x12a0 kernel/workqueue.c:2441
  kthread+0x29d/0x330 kernel/kthread.c:376
  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
irq event stamp: 282074
hardirqs last  enabled at (282074): [<ffffffff8154733a>] __cancel_work_timer+0x36a/0x560 kernel/workqueue.c:3156
hardirqs last disabled at (282073): [<ffffffff81543cda>] try_to_grab_pending+0xfa/0x890 kernel/workqueue.c:1267
softirqs last  enabled at (282002): [<ffffffff814f495b>] __do_softirq kernel/softirq.c:630 [inline]
softirqs last  enabled at (282002): [<ffffffff814f495b>] invoke_softirq kernel/softirq.c:470 [inline]
softirqs last  enabled at (282002): [<ffffffff814f495b>] __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:679
softirqs last disabled at (282009): [<ffffffff814f495b>] __do_softirq kernel/softirq.c:630 [inline]
softirqs last disabled at (282009): [<ffffffff814f495b>] invoke_softirq kernel/softirq.c:470 [inline]
softirqs last disabled at (282009): [<ffffffff814f495b>] __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:679

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

       CPU0
       ----
  lock((work_completion)(&(&host->detect)->work));
  <Interrupt>
    lock((work_completion)(&(&host->detect)->work));

 *** DEADLOCK ***

1 lock held by swapper/0/0:
 #0: ffffc90000007bc0 ((&vub300->inactivity_timer)){+.-.}-{0:0}, at: call_timer_fn+0xcf/0x670 kernel/time/timer.c:1698

stack backtrace:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <IRQ>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:3974
 mark_lock_irq+0xa9/0x900 kernel/locking/lockdep.c:4177
 mark_lock+0x208/0x320 kernel/locking/lockdep.c:4633
 mark_usage kernel/locking/lockdep.c:-1 [inline]
 __lock_acquire+0xce0/0x7c40 kernel/locking/lockdep.c:5017
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
 __flush_work+0x122/0xac0 kernel/workqueue.c:3072
 __cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3163
 mmc_free_host+0x15/0x30 drivers/mmc/core/host.c:672
 call_timer_fn+0x1ac/0x670 kernel/time/timer.c:1701
 expire_timers kernel/time/timer.c:1752 [inline]
 __run_timers+0x56c/0x810 kernel/time/timer.c:2023
 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:2036
 handle_softirqs+0x291/0x910 kernel/softirq.c:596
 __do_softirq kernel/softirq.c:630 [inline]
 invoke_softirq kernel/softirq.c:470 [inline]
 __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:679
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:691
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
 sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1118
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:742
Code: 48 89 df e8 17 47 99 f7 e9 44 ff ff ff e8 fd 03 f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 66 90 0f 00 2d 57 93 4c 00 fb f4 <c3> 0f 1f 40 00 41 57 41 56 53 49 be 00 00 00 00 00 fc ff df 65 48
RSP: 0018:ffffffff8c807d88 EFLAGS: 000002c6
RAX: 8fc675a282020100 RBX: ffffffff8a3a18b7 RCX: 8fc675a282020100
RDX: 0000000000000001 RSI: ffffffff8a8c17a0 RDI: ffffffff8adf5de0
RBP: ffffffff8c807ec0 R08: ffff8880b8e3580b R09: 1ffff110171c6b01
R10: dffffc0000000000 R11: ffffed10171c6b02 R12: 0000000000000000
R13: dffffc0000000000 R14: ffffffff8c8bc740 R15: 1ffffffff1900fbc
 default_idle_call+0x84/0xc0 kernel/sched/idle.c:109
 cpuidle_idle_call kernel/sched/idle.c:199 [inline]
 do_idle+0x250/0x680 kernel/sched/idle.c:323
 cpu_startup_entry+0x3f/0x60 kernel/sched/idle.c:422
 rest_init+0x2dc/0x300 init/main.c:745
 arch_call_rest_init+0xa/0xa init/main.c:904
 start_kernel+0x493/0x53c init/main.c:1151
 secondary_startup_64_no_verify+0xcf/0xdb
 </TASK>
BUG: sleeping function called from invalid context at kernel/workqueue.c:3013
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 0, name: swapper/0
preempt_count: 101, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff8a38b729>] schedule_preempt_disabled+0x19/0x20 kernel/sched/core.c:6699
CPU: 0 PID: 0 Comm: swapper/0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <IRQ>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 __might_resched+0x489/0x5f0 kernel/sched/core.c:9970
 start_flush_work kernel/workqueue.c:3013 [inline]
 __flush_work+0x142/0xac0 kernel/workqueue.c:3075
 __cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3163
 mmc_free_host+0x15/0x30 drivers/mmc/core/host.c:672
 call_timer_fn+0x1ac/0x670 kernel/time/timer.c:1701
 expire_timers kernel/time/timer.c:1752 [inline]
 __run_timers+0x56c/0x810 kernel/time/timer.c:2023
 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:2036
 handle_softirqs+0x291/0x910 kernel/softirq.c:596
 __do_softirq kernel/softirq.c:630 [inline]
 invoke_softirq kernel/softirq.c:470 [inline]
 __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:679
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:691
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
 sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1118
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:742
Code: 48 89 df e8 17 47 99 f7 e9 44 ff ff ff e8 fd 03 f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 66 90 0f 00 2d 57 93 4c 00 fb f4 <c3> 0f 1f 40 00 41 57 41 56 53 49 be 00 00 00 00 00 fc ff df 65 48
RSP: 0018:ffffffff8c807d88 EFLAGS: 000002c6
RAX: 8fc675a282020100 RBX: ffffffff8a3a18b7 RCX: 8fc675a282020100
RDX: 0000000000000001 RSI: ffffffff8a8c17a0 RDI: ffffffff8adf5de0
RBP: ffffffff8c807ec0 R08: ffff8880b8e3580b R09: 1ffff110171c6b01
R10: dffffc0000000000 R11: ffffed10171c6b02 R12: 0000000000000000
R13: dffffc0000000000 R14: ffffffff8c8bc740 R15: 1ffffffff1900fbc
 default_idle_call+0x84/0xc0 kernel/sched/idle.c:109
 cpuidle_idle_call kernel/sched/idle.c:199 [inline]
 do_idle+0x250/0x680 kernel/sched/idle.c:323
 cpu_startup_entry+0x3f/0x60 kernel/sched/idle.c:422
 rest_init+0x2dc/0x300 init/main.c:745
 arch_call_rest_init+0xa/0xa init/main.c:904
 start_kernel+0x493/0x53c init/main.c:1151
 secondary_startup_64_no_verify+0xcf/0xdb
 </TASK>
ODEBUG: object ffffc900000079a0 is NOT on stack ffffffff8c800000, but annotated.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 0 at lib/debugobjects.c:558 debug_object_is_on_stack lib/debugobjects.c:-1 [inline]
WARNING: CPU: 0 PID: 0 at lib/debugobjects.c:558 lookup_object_or_alloc lib/debugobjects.c:591 [inline]
WARNING: CPU: 0 PID: 0 at lib/debugobjects.c:558 __debug_object_init+0x18e/0x440 lib/debugobjects.c:672
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W          syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:debug_object_is_on_stack lib/debugobjects.c:558 [inline]
RIP: 0010:lookup_object_or_alloc lib/debugobjects.c:591 [inline]
RIP: 0010:__debug_object_init+0x18e/0x440 lib/debugobjects.c:672
Code: 24 04 74 2f 41 ff c6 44 89 35 0e fc dd 12 48 c7 c1 80 66 df 8a 48 c7 c7 e0 66 df 8a 84 c0 48 0f 45 f9 48 89 de e8 e2 cb 0a 06 <0f> 0b eb 05 4c 8b 7c 24 18 4d 8d 65 10 4d 89 e6 49 c1 ee 03 41 0f
RSP: 0018:ffffc90000007908 EFLAGS: 00010046
RAX: 0000000000000050 RBX: ffffc900000079a0 RCX: 8fc675a282020100
RDX: 0000000000000100 RSI: 0000000000000102 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffc90000007607 R09: 1ffff92000000ec0
R10: dffffc0000000000 R11: fffff52000000ec1 R12: ffffffff8c8bc760
R13: ffff88805a90f1f8 R14: 0000000000000001 R15: ffffffff8a8d3020
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000558a092aafb0 CR3: 00000000272a2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <IRQ>
 __synchronize_srcu+0x227/0x350 kernel/rcu/srcutree.c:1241
 wakeup_source_remove drivers/base/power/wakeup.c:198 [inline]
 wakeup_source_unregister+0x112/0x190 drivers/base/power/wakeup.c:242
 mmc_host_classdev_release+0x43/0xf0 drivers/mmc/core/host.c:77
 device_release+0x92/0x1c0 drivers/base/core.c:-1
 kobject_cleanup lib/kobject.c:681 [inline]
 kobject_release lib/kobject.c:712 [inline]
 kref_put include/linux/kref.h:65 [inline]
 kobject_put+0x217/0x450 lib/kobject.c:729
 call_timer_fn+0x1ac/0x670 kernel/time/timer.c:1701
 expire_timers kernel/time/timer.c:1752 [inline]
 __run_timers+0x56c/0x810 kernel/time/timer.c:2023
 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:2036
 handle_softirqs+0x291/0x910 kernel/softirq.c:596
 __do_softirq kernel/softirq.c:630 [inline]
 invoke_softirq kernel/softirq.c:470 [inline]
 __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:679
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:691
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
 sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1118
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:742
Code: 48 89 df e8 17 47 99 f7 e9 44 ff ff ff e8 fd 03 f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 66 90 0f 00 2d 57 93 4c 00 fb f4 <c3> 0f 1f 40 00 41 57 41 56 53 49 be 00 00 00 00 00 fc ff df 65 48
RSP: 0018:ffffffff8c807d88 EFLAGS: 000002c6
RAX: 8fc675a282020100 RBX: ffffffff8a3a18b7 RCX: 8fc675a282020100
RDX: 0000000000000001 RSI: ffffffff8a8c17a0 RDI: ffffffff8adf5de0
RBP: ffffffff8c807ec0 R08: ffff8880b8e3580b R09: 1ffff110171c6b01
R10: dffffc0000000000 R11: ffffed10171c6b02 R12: 0000000000000000
R13: dffffc0000000000 R14: ffffffff8c8bc740 R15: 1ffffffff1900fbc
 default_idle_call+0x84/0xc0 kernel/sched/idle.c:109
 cpuidle_idle_call kernel/sched/idle.c:199 [inline]
 do_idle+0x250/0x680 kernel/sched/idle.c:323
 cpu_startup_entry+0x3f/0x60 kernel/sched/idle.c:422
 rest_init+0x2dc/0x300 init/main.c:745
 arch_call_rest_init+0xa/0xa init/main.c:904
 start_kernel+0x493/0x53c init/main.c:1151
 secondary_startup_64_no_verify+0xcf/0xdb
 </TASK>
----------------
Code disassembly (best guess):
   0:	48 89 df             	mov    %rbx,%rdi
   3:	e8 17 47 99 f7       	call   0xf799471f
   8:	e9 44 ff ff ff       	jmp    0xffffff51
   d:	e8 fd 03 f6 ff       	call   0xfff6040f
  12:	00 00                	add    %al,(%rax)
  14:	cc                   	int3
  15:	cc                   	int3
  16:	00 00                	add    %al,(%rax)
  18:	cc                   	int3
  19:	cc                   	int3
  1a:	00 00                	add    %al,(%rax)
  1c:	cc                   	int3
  1d:	cc                   	int3
  1e:	00 66 90             	add    %ah,-0x70(%rsi)
  21:	0f 00 2d 57 93 4c 00 	verw   0x4c9357(%rip)        # 0x4c937f
  28:	fb                   	sti
  29:	f4                   	hlt
* 2a:	c3                   	ret <-- trapping instruction
  2b:	0f 1f 40 00          	nopl   0x0(%rax)
  2f:	41 57                	push   %r15
  31:	41 56                	push   %r14
  33:	53                   	push   %rbx
  34:	49 be 00 00 00 00 00 	movabs $0xdffffc0000000000,%r14
  3b:	fc ff df
  3e:	65                   	gs
  3f:	48                   	rex.W

Crashes (418):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/09 03:49 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/04/19 01:04 linux-6.1.y 7c87defbd336 303e2802 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
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
2026/08/15 07:25 linux-6.1.y e4f7d8be268e 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/15 04:59 linux-6.1.y e4f7d8be268e 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/14 22:55 linux-6.1.y e4f7d8be268e 6f9b3e89 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/14 17:04 linux-6.1.y e4f7d8be268e 6f9b3e89 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/14 01:40 linux-6.1.y e4f7d8be268e b13552fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/13 21:15 linux-6.1.y e4f7d8be268e b13552fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/13 21:15 linux-6.1.y e4f7d8be268e b13552fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/12 23:06 linux-6.1.y e4f7d8be268e 359b2492 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/12 09:13 linux-6.1.y e4f7d8be268e f8d35649 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/12 07:22 linux-6.1.y e4f7d8be268e f8d35649 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/11 21:50 linux-6.1.y e4f7d8be268e 71790083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/11 18:41 linux-6.1.y e4f7d8be268e 71790083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/11 03:44 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/11 00:18 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/11 00:18 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/10 13:22 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/10 11:00 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/10 07:38 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/09 16:28 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/08 07:49 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/07 15:16 linux-6.1.y e4f7d8be268e e4ef95d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/06 22:36 linux-6.1.y 03f3a99e8e93 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/06 17:50 linux-6.1.y fb28aa725e05 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/06 04:17 linux-6.1.y fb28aa725e05 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/06 00:31 linux-6.1.y fb28aa725e05 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/06 00:31 linux-6.1.y fb28aa725e05 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/05 18:16 linux-6.1.y fb28aa725e05 52aa2820 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/05 08:16 linux-6.1.y fb28aa725e05 52aa2820 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/05 01:40 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/04 22:41 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/04 19:16 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/04 04:32 linux-6.1.y fb28aa725e05 9451e17e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/08/03 21:57 linux-6.1.y fb28aa725e05 6b7c9f71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/05/25 16:14 linux-6.1.y dcbcab9d7079 c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/05/25 04:58 linux-6.1.y dcbcab9d7079 c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/05/24 06:01 linux-6.1.y dcbcab9d7079 c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/05/21 06:35 linux-6.1.y c27210688955 41b8c833 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/05/17 22:56 linux-6.1.y c27210688955 de5aae85 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/04/28 05:36 linux-6.1.y 7c87defbd336 ce741359 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/04/21 02:30 linux-6.1.y 7c87defbd336 e65da4ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2026/04/18 18:41 linux-6.1.y 7c87defbd336 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/10/17 11:18 linux-6.1.y aa4cd140bba5 666f77ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/10/16 12:35 linux-6.1.y aa4cd140bba5 bde2d81c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/10/01 16:29 linux-6.1.y aa4cd140bba5 ea2b66a6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/09/26 22:24 linux-6.1.y e526b12bf916 9314348a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/09/24 02:51 linux-6.1.y e526b12bf916 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/08/01 02:12 linux-6.1.y c1cec4dad96b 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan inconsistent lock state in valid_state
2024/07/26 17:31 linux-6.1.y c18e82d3ee44 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf inconsistent lock state in valid_state
* Struck through repros no longer work on HEAD.