inconsistent lock state in valid_state (3)

Status: upstream: reported C repro on 2026/04/20 22:51
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+c8eb6060abf5a2a7b274@syzkaller.appspotmail.com
Fix commit: b2606c302d7f phonet/pep: disable BH around forwarded sk_receive_skb()
Patched on: [ci2-linux-5-15-kasan ci2-linux-5-15-kasan-perf], missing on: [ci2-linux-5-15-kasan-arm64]
First crash: 147d, last: 17d
Fix bisection: fixed by (bisect log) :
commit b2606c302d7f2b4ee48da05e32ed60aed1b0cd53
Author: Zijing Yin <yzjaurora@gmail.com>
Date: Tue May 19 17:26:33 2026 +0000

  phonet/pep: disable BH around forwarded sk_receive_skb()

  
Bug presence (1)
Date Name Commit Repro Result
2026/04/22 upstream (ToT) 6596a02b2078 C [report] inconsistent lock state in __sk_receive_skb
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 697d 915d 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 syz, C 54 18d 40d 0/2 upstream: reported C repro on 2026/08/05 10:00
linux-6.6 inconsistent lock state in valid_state origin:upstream 4 syz, C done 19 109d 149d 2/2 fixed on 2026/06/29 10:59
upstream inconsistent lock state in valid_state (7) prio:high x25 4 syz, C 426 17d 35d 0/29 upstream: reported C repro on 2026/08/11 00:12
upstream inconsistent lock state in valid_state (6) kernfs comedi 4 2 331d 330d 0/29 auto-obsoleted due to no activity on 2026/01/26 19:03
upstream inconsistent lock state in valid_state kernel 4 1 1299d 1295d 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 581d 756d 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 1188d 1267d 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 4 syz, C done 581 17d 1088d 0/3 upstream: reported C repro on 2023/09/22 23:56
upstream inconsistent lock state in valid_state (5) net 4 515 376d 381d 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 826d 951d 25/29 fixed on 2024/06/11 03:41
upstream inconsistent lock state in valid_state (3) mm 4 syz, C error 376 773d 822d 27/29 fixed on 2024/08/14 03:44
linux-6.1 inconsistent lock state in valid_state 4 1 1269d 1269d 0/3 auto-obsoleted due to no activity on 2023/07/24 01:34
Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/06/10 06:45 22m retest repro linux-5.15.y no crash log
2026/06/10 06:45 22m retest repro linux-5.15.y no crash log
2026/06/10 06:45 23m retest repro linux-5.15.y no crash log
2026/06/10 06:45 23m retest repro linux-5.15.y no crash log
2026/06/10 06:45 36m retest repro linux-5.15.y no crash log
2026/06/09 16:45 24m retest repro linux-5.15.y no crash log
2026/06/09 16:45 24m retest repro linux-5.15.y no crash log
2026/06/09 16:45 43m retest repro linux-5.15.y no crash log
2026/06/09 16:45 35m retest repro linux-5.15.y no crash log
2026/06/09 16:45 29m retest repro linux-5.15.y no crash log

Sample crash report:
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
swapper/1/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff88807c254710 ((work_completion)(&(&host->detect)->work)){+.?.}-{0:0}, at: __flush_work+0xfa/0x210 kernel/workqueue.c:3090
{SOFTIRQ-ON-W} state was registered at:
  lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
  process_one_work+0x7ba/0xff0 kernel/workqueue.c:2286
  worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
  kthread+0x42e/0x520 kernel/kthread.c:334
  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
irq event stamp: 206180
hardirqs last  enabled at (206180): [<ffffffff814e1b9a>] __cancel_work_timer+0x36a/0x560 kernel/workqueue.c:3174
hardirqs last disabled at (206179): [<ffffffff814dee4b>] try_to_grab_pending+0xfb/0x820 kernel/workqueue.c:1272
softirqs last  enabled at (206084): [<ffffffff814933fb>] __do_softirq kernel/softirq.c:610 [inline]
softirqs last  enabled at (206084): [<ffffffff814933fb>] invoke_softirq kernel/softirq.c:450 [inline]
softirqs last  enabled at (206084): [<ffffffff814933fb>] __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
softirqs last disabled at (206109): [<ffffffff814933fb>] __do_softirq kernel/softirq.c:610 [inline]
softirqs last disabled at (206109): [<ffffffff814933fb>] invoke_softirq kernel/softirq.c:450 [inline]
softirqs last disabled at (206109): [<ffffffff814933fb>] __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659

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/1/0:
 #0: ffffc90000dd0bc0 ((&vub300->inactivity_timer)){+.-.}-{0:0}, at: lockdep_copy_map include/linux/lockdep.h:45 [inline]
 #0: ffffc90000dd0bc0 ((&vub300->inactivity_timer)){+.-.}-{0:0}, at: call_timer_fn+0xca/0x540 kernel/time/timer.c:1638

stack backtrace:
CPU: 1 PID: 0 Comm: swapper/1 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/0x250 lib/dump_stack.c:106
 valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:3932
 mark_lock_irq+0xa9/0x900 kernel/locking/lockdep.c:4135
 mark_lock+0x208/0x320 kernel/locking/lockdep.c:4591
 mark_usage kernel/locking/lockdep.c:-1 [inline]
 __lock_acquire+0xc63/0x7b50 kernel/locking/lockdep.c:4966
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 __flush_work+0x116/0x210 kernel/workqueue.c:3090
 __cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3181
 mmc_free_host+0x15/0x30 drivers/mmc/core/host.c:663
 call_timer_fn+0x17b/0x540 kernel/time/timer.c:1648
 expire_timers kernel/time/timer.c:1699 [inline]
 __run_timers+0x56c/0x810 kernel/time/timer.c:1970
 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1983
 handle_softirqs+0x336/0x830 kernel/softirq.c:576
 __do_softirq kernel/softirq.c:610 [inline]
 invoke_softirq kernel/softirq.c:450 [inline]
 __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
 sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:730
Code: b7 48 89 df e8 36 b7 f4 f7 eb ad e8 df ab f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 00 cc 66 90 0f 00 2d e7 65 5c 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:ffffc90000d67d48 EFLAGS: 000002c2
RAX: 69a99887e517c000 RBX: ffff88813fe70000 RCX: 69a99887e517c000
RDX: 0000000000000001 RSI: ffffffff8a2b2be0 RDI: ffffffff8a7a4200
RBP: ffffc90000d67e80 R08: ffff8880b913b30b R09: 1ffff11017227661
R10: dffffc0000000000 R11: ffffed1017227662 R12: 1ffff920001acfb4
R13: dffffc0000000000 R14: 1ffff11027fce000 R15: 0000000000000000
 default_idle_call+0x81/0xc0 kernel/sched/idle.c:112
 cpuidle_idle_call kernel/sched/idle.c:202 [inline]
 do_idle+0x3a1/0x650 kernel/sched/idle.c:326
 cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:424
 start_secondary+0x32f/0x430 arch/x86/kernel/smpboot.c:281
 secondary_startup_64_no_verify+0xb1/0xbb
 </TASK>
BUG: sleeping function called from invalid context at kernel/workqueue.c:3031
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 0, name: swapper/1
INFO: lockdep is turned off.
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 1 PID: 0 Comm: swapper/1 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/0x250 lib/dump_stack.c:106
 ___might_sleep+0x493/0x610 kernel/sched/core.c:9658
 start_flush_work+0x2e/0x830 kernel/workqueue.c:3031
 __flush_work+0x148/0x210 kernel/workqueue.c:3093
 __cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3181
 mmc_free_host+0x15/0x30 drivers/mmc/core/host.c:663
 call_timer_fn+0x17b/0x540 kernel/time/timer.c:1648
 expire_timers kernel/time/timer.c:1699 [inline]
 __run_timers+0x56c/0x810 kernel/time/timer.c:1970
 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1983
 handle_softirqs+0x336/0x830 kernel/softirq.c:576
 __do_softirq kernel/softirq.c:610 [inline]
 invoke_softirq kernel/softirq.c:450 [inline]
 __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
 sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:730
Code: b7 48 89 df e8 36 b7 f4 f7 eb ad e8 df ab f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 00 cc 66 90 0f 00 2d e7 65 5c 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:ffffc90000d67d48 EFLAGS: 000002c2
RAX: 69a99887e517c000 RBX: ffff88813fe70000 RCX: 69a99887e517c000
RDX: 0000000000000001 RSI: ffffffff8a2b2be0 RDI: ffffffff8a7a4200
RBP: ffffc90000d67e80 R08: ffff8880b913b30b R09: 1ffff11017227661
R10: dffffc0000000000 R11: ffffed1017227662 R12: 1ffff920001acfb4
R13: dffffc0000000000 R14: 1ffff11027fce000 R15: 0000000000000000
 default_idle_call+0x81/0xc0 kernel/sched/idle.c:112
 cpuidle_idle_call kernel/sched/idle.c:202 [inline]
 do_idle+0x3a1/0x650 kernel/sched/idle.c:326
 cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:424
 start_secondary+0x32f/0x430 arch/x86/kernel/smpboot.c:281
 secondary_startup_64_no_verify+0xb1/0xbb
 </TASK>
ODEBUG: object ffffc90000dd09a0 is NOT on stack ffffc90000d60000, but annotated.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 0 at lib/debugobjects.c:561 debug_object_is_on_stack lib/debugobjects.c:-1 [inline]
WARNING: CPU: 1 PID: 0 at lib/debugobjects.c:561 lookup_object_or_alloc lib/debugobjects.c:594 [inline]
WARNING: CPU: 1 PID: 0 at lib/debugobjects.c:561 __debug_object_init+0x4c0/0xc80 lib/debugobjects.c:621
Modules linked in:
CPU: 1 PID: 0 Comm: swapper/1 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:561 [inline]
RIP: 0010:lookup_object_or_alloc lib/debugobjects.c:594 [inline]
RIP: 0010:__debug_object_init+0x4c0/0xc80 lib/debugobjects.c:621
Code: d6 2d 73 12 48 c7 c1 00 4a 7a 8a 48 c7 c7 60 4a 7a 8a 84 c0 48 0f 45 f9 4c 89 ee e8 ea b7 c8 05 48 be 00 00 00 00 00 fc ff df <0f> 0b e9 4d fd ff ff 83 3d 02 2d 73 12 00 4c 89 6c 24 28 0f 84 23
RSP: 0018:ffffc90000dd07e0 EFLAGS: 00010046
RAX: 0000000000000050 RBX: 0000000000000001 RCX: 69a99887e517c000
RDX: 0000000000000100 RSI: dffffc0000000000 RDI: 0000000000000000
RBP: ffffc90000dd0950 R08: ffffc90000dd0307 R09: 1ffff920001ba060
R10: dffffc0000000000 R11: fffff520001ba061 R12: f8f8f8f8f8f8f8f8
R13: ffffc90000dd09a0 R14: ffff88813fe70020 R15: ffff88807ae9cb28
FS:  0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd58ed727c0 CR3: 000000007e097000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <IRQ>
 __synchronize_srcu+0x229/0x350 kernel/rcu/srcutree.c:928
 wakeup_source_remove drivers/base/power/wakeup.c:203 [inline]
 wakeup_source_unregister+0x112/0x190 drivers/base/power/wakeup.c:247
 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:713 [inline]
 kobject_release lib/kobject.c:744 [inline]
 kref_put include/linux/kref.h:65 [inline]
 kobject_put+0x217/0x450 lib/kobject.c:761
 call_timer_fn+0x17b/0x540 kernel/time/timer.c:1648
 expire_timers kernel/time/timer.c:1699 [inline]
 __run_timers+0x56c/0x810 kernel/time/timer.c:1970
 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1983
 handle_softirqs+0x336/0x830 kernel/softirq.c:576
 __do_softirq kernel/softirq.c:610 [inline]
 invoke_softirq kernel/softirq.c:450 [inline]
 __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
 sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:730
Code: b7 48 89 df e8 36 b7 f4 f7 eb ad e8 df ab f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 00 cc 66 90 0f 00 2d e7 65 5c 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:ffffc90000d67d48 EFLAGS: 000002c2
RAX: 69a99887e517c000 RBX: ffff88813fe70000 RCX: 69a99887e517c000
RDX: 0000000000000001 RSI: ffffffff8a2b2be0 RDI: ffffffff8a7a4200
RBP: ffffc90000d67e80 R08: ffff8880b913b30b R09: 1ffff11017227661
R10: dffffc0000000000 R11: ffffed1017227662 R12: 1ffff920001acfb4
R13: dffffc0000000000 R14: 1ffff11027fce000 R15: 0000000000000000
 default_idle_call+0x81/0xc0 kernel/sched/idle.c:112
 cpuidle_idle_call kernel/sched/idle.c:202 [inline]
 do_idle+0x3a1/0x650 kernel/sched/idle.c:326
 cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:424
 start_secondary+0x32f/0x430 arch/x86/kernel/smpboot.c:281
 secondary_startup_64_no_verify+0xb1/0xbb
 </TASK>
----------------
Code disassembly (best guess):
   0:	b7 48                	mov    $0x48,%bh
   2:	89 df                	mov    %ebx,%edi
   4:	e8 36 b7 f4 f7       	call   0xf7f4b73f
   9:	eb ad                	jmp    0xffffffb8
   b:	e8 df ab f6 ff       	call   0xfff6abef
  10:	00 00                	add    %al,(%rax)
  12:	cc                   	int3
  13:	cc                   	int3
  14:	00 00                	add    %al,(%rax)
  16:	cc                   	int3
  17:	cc                   	int3
  18:	00 00                	add    %al,(%rax)
  1a:	cc                   	int3
  1b:	cc                   	int3
  1c:	00 00                	add    %al,(%rax)
  1e:	cc                   	int3
  1f:	66 90                	xchg   %ax,%ax
  21:	0f 00 2d e7 65 5c 00 	verw   0x5c65e7(%rip)        # 0x5c660f
  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 (303):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/18 17:06 linux-5.15.y aabd761612db 1e72964b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/18 15:38 linux-5.15.y aabd761612db 1e72964b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/18 13:56 linux-5.15.y aabd761612db 1e72964b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/28 11:54 linux-5.15.y 28c35638ec51 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/28 10:01 linux-5.15.y 28c35638ec51 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/28 00:13 linux-5.15.y 4a1eaf96ee5c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/27 18:21 linux-5.15.y 4a1eaf96ee5c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/27 03:45 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/26 20:15 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/26 17:53 linux-5.15.y 945fa863f02c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/26 09:55 linux-5.15.y 945fa863f02c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/26 09:03 linux-5.15.y 945fa863f02c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/26 07:37 linux-5.15.y 945fa863f02c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/26 06:01 linux-5.15.y 945fa863f02c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/26 04:58 linux-5.15.y 945fa863f02c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/25 17:41 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/25 15:49 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/25 15:09 linux-5.15.y 945fa863f02c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/25 09:50 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/25 06:58 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/25 04:50 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/25 03:28 linux-5.15.y 945fa863f02c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/24 19:47 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/24 17:55 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/24 16:51 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/24 15:01 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/23 18:18 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/23 18:07 linux-5.15.y 945fa863f02c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/23 12:04 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/22 18:50 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/22 09:17 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/22 04:47 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/21 17:49 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/20 20:06 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/19 21:52 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/19 20:26 linux-5.15.y 0eb903b5b519 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/19 01:09 linux-5.15.y aabd761612db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/18 22:19 linux-5.15.y aabd761612db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/18 18:06 linux-5.15.y aabd761612db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/18 04:53 linux-5.15.y aabd761612db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/18 04:46 linux-5.15.y aabd761612db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/18 03:38 linux-5.15.y aabd761612db 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/17 19:21 linux-5.15.y aabd761612db 905244d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/17 14:36 linux-5.15.y aabd761612db 905244d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/08/17 13:24 linux-5.15.y aabd761612db 905244d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 11:43 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 10:33 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 09:18 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 08:01 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 04:32 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/24 02:41 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/22 22:15 linux-5.15.y 93741761e5e3 5f091fcc .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/22 09:11 linux-5.15.y 93741761e5e3 70ae9b03 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/05/03 16:07 linux-5.15.y ef251c45f1cd a0d91488 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/21 03:00 linux-5.15.y b9d57c40a767 e65da4ee .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan inconsistent lock state in valid_state
2026/04/20 22:50 linux-5.15.y b9d57c40a767 e65da4ee .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.