syzbot


inconsistent lock state in trie_delete_elem

Status: upstream: reported C repro on 2025/12/04 17:55
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+644bfebcf8f53278b7e5@syzkaller.appspotmail.com
First crash: 161d, last: 11h24m
Bug presence (2)
Date Name Commit Repro Result
2025/12/05 linux-5.15.y (ToT) cc5ec8769306 C [report] inconsistent lock state in trie_delete_elem
2025/12/05 upstream (ToT) 7203ca412fc8 C Didn't crash
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 inconsistent lock state in trie_delete_elem origin:lts-only 4 C error 12 10d 161d 0/3 upstream: reported C repro on 2025/12/04 16:53
linux-6.6 inconsistent lock state in trie_delete_elem origin:lts-only 4 C error 42 10h26m 161d 0/2 upstream: reported C repro on 2025/12/04 20:31
Fix bisection attempts (4)
Created Duration User Patch Repo Result
2026/04/26 04:31 37m fix candidate upstream error job log
2026/03/24 00:20 1h30m fix candidate upstream error job log
2026/02/21 07:21 7m fix candidate upstream error job log
2026/01/21 17:52 3m fix candidate upstream error job log

Sample crash report:
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {INITIAL USE} -> {IN-NMI} usage.
syz.0.23/4334 [HC1[1]:SC0[0]:HE0:SE1] takes:
ffff888078c2ea38 (&trie->lock){....}-{2:2}, at: trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467
{INITIAL USE} state was registered at:
  lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
  __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
  _raw_spin_lock_irqsave+0xb0/0x100 kernel/locking/spinlock.c:162
  trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467
  0xffffffffa001693a
  bpf_dispatcher_nop_func include/linux/bpf.h:888 [inline]
  __bpf_prog_run include/linux/filter.h:628 [inline]
  bpf_prog_run include/linux/filter.h:635 [inline]
  bpf_overflow_handler+0x1c2/0x4a0 kernel/events/core.c:10297
  __perf_event_overflow+0x364/0x530 kernel/events/core.c:9515
  perf_swevent_overflow kernel/events/core.c:9591 [inline]
  perf_swevent_event+0x4ad/0x530 kernel/events/core.c:9629
  perf_bp_event+0x276/0x320 kernel/events/core.c:10484
  hw_breakpoint_handler arch/x86/kernel/hw_breakpoint.c:555 [inline]
  hw_breakpoint_exceptions_notify+0x152/0x470 arch/x86/kernel/hw_breakpoint.c:586
  notifier_call_chain kernel/notifier.c:83 [inline]
  atomic_notifier_call_chain+0x15d/0x280 kernel/notifier.c:198
  notify_die+0x141/0x1a0 kernel/notifier.c:529
  notify_debug+0x20/0x30 arch/x86/kernel/traps.c:872
  exc_debug_user arch/x86/kernel/traps.c:998 [inline]
  noist_exc_debug+0x73/0x120 arch/x86/kernel/traps.c:1035
  asm_exc_debug+0x2f/0x40 arch/x86/include/asm/idtentry.h:642
irq event stamp: 2814
hardirqs last  enabled at (2813): [<ffffffff89bca248>] do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
hardirqs last disabled at (2814): [<ffffffff89bcb659>] exc_debug_user arch/x86/kernel/traps.c:972 [inline]
hardirqs last disabled at (2814): [<ffffffff89bcb659>] noist_exc_debug+0x49/0x120 arch/x86/kernel/traps.c:1035
softirqs last  enabled at (2776): [<ffffffff8186edf9>] bpf_prog_load+0x10f9/0x1510 kernel/bpf/syscall.c:2380
softirqs last disabled at (2774): [<ffffffff81854ff9>] spin_lock_bh include/linux/spinlock.h:369 [inline]
softirqs last disabled at (2774): [<ffffffff81854ff9>] bpf_ksym_add+0x29/0x340 kernel/bpf/core.c:633

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

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

 *** DEADLOCK ***

2 locks held by syz.0.23/4334:
 #0: ffffffff8c31eb20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:313
 #1: ffffffff8c31eb20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:313

stack backtrace:
CPU: 1 PID: 4334 Comm: syz.0.23 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
 <#DB>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 lock_acquire+0x2c3/0x400 kernel/locking/lockdep.c:5614
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xb0/0x100 kernel/locking/spinlock.c:162
 trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467
 bpf_prog_2c29ac5cdc6b1842+0x3a/0x508
 bpf_dispatcher_nop_func include/linux/bpf.h:888 [inline]
 __bpf_prog_run include/linux/filter.h:628 [inline]
 bpf_prog_run include/linux/filter.h:635 [inline]
 bpf_overflow_handler+0x1c2/0x4a0 kernel/events/core.c:10297
 __perf_event_overflow+0x364/0x530 kernel/events/core.c:9515
 perf_swevent_overflow kernel/events/core.c:9591 [inline]
 perf_swevent_event+0x4ad/0x530 kernel/events/core.c:9629
 perf_bp_event+0x276/0x320 kernel/events/core.c:10484
 hw_breakpoint_handler arch/x86/kernel/hw_breakpoint.c:555 [inline]
 hw_breakpoint_exceptions_notify+0x152/0x470 arch/x86/kernel/hw_breakpoint.c:586
 notifier_call_chain kernel/notifier.c:83 [inline]
 atomic_notifier_call_chain+0x15d/0x280 kernel/notifier.c:198
 notify_die+0x141/0x1a0 kernel/notifier.c:529
 notify_debug+0x20/0x30 arch/x86/kernel/traps.c:872
 exc_debug_kernel arch/x86/kernel/traps.c:929 [inline]
 exc_debug+0xcf/0x130 arch/x86/kernel/traps.c:1029
 asm_exc_debug+0x1a/0x40 arch/x86/include/asm/idtentry.h:642
RIP: 0010:__get_user_nocheck_8+0x9/0x13 arch/x86/lib/getuser.S:160
Code: 90 0f 01 cb 0f ae e8 0f b7 10 31 c0 0f 01 ca c3 90 0f 01 cb 0f ae e8 8b 10 31 c0 0f 01 ca c3 90 90 0f 01 cb 0f ae e8 48 8b 10 <31> c0 0f 01 ca c3 90 0f 01 ca 31 d2 48 c7 c0 f2 ff ff ff c3 00 00
RSP: 0000:ffffc90002f5f4c0 EFLAGS: 00040806
RAX: 0000200000000300 RBX: 0000000000000000 RCX: ffff888027e28000
RDX: 00006370692f736e RSI: 0000200000000300 RDI: 00007fffffffeff0
RBP: 0000000000000007 R08: ffffffff8d89f06f R09: 1ffffffff1b13e0d
R10: dffffc0000000000 R11: fffffbfff1b13e0e R12: 0000200000000300
R13: 00007fffffffeff0 R14: 00000000ffffffff R15: dffffc0000000000
 </#DB>
 <TASK>
 perf_callchain_user+0x40e/0xfd0 arch/x86/events/core.c:2900
 get_perf_callchain+0x33d/0x460 kernel/events/callchain.c:221
 perf_callchain kernel/events/core.c:7606 [inline]
 perf_prepare_sample+0x352/0x1cd0 kernel/events/core.c:7633
 __perf_event_output kernel/events/core.c:7802 [inline]
 perf_event_output_forward+0x185/0x2e0 kernel/events/core.c:7822
 __perf_event_overflow+0x364/0x530 kernel/events/core.c:9515
 perf_tp_event+0x383/0xbf0 kernel/events/core.c:10047
 perf_trace_run_bpf_submit+0xf3/0x1c0 kernel/events/core.c:10021
 perf_trace_lock+0x301/0x390 include/trace/events/lock.h:39
 trace_lock_release include/trace/events/lock.h:58 [inline]
 lock_release+0x84a/0x8a0 kernel/locking/lockdep.c:5634
 rcu_read_unlock include/linux/rcupdate.h:773 [inline]
 atomic_notifier_call_chain+0x260/0x280 kernel/notifier.c:199
 notify_die+0x141/0x1a0 kernel/notifier.c:529
 notify_debug+0x20/0x30 arch/x86/kernel/traps.c:872
 exc_debug_user arch/x86/kernel/traps.c:998 [inline]
 noist_exc_debug+0x73/0x120 arch/x86/kernel/traps.c:1035
 asm_exc_debug+0x2f/0x40 arch/x86/include/asm/idtentry.h:642
RIP: 0033:0x7f85f8629b7d
Code: 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 27 01 00 00 c5 fd 74 0f <c5> fd d7 c1 85 c0 74 5b f3 0f bc c0 e9 30 01 00 00 66 90 f3 0f bc
RSP: 002b:00007ffc1f2361b8 EFLAGS: 00000283
RAX: 0000000000000300 RBX: 00007ffc1f2366f0 RCX: 2f666c65732f636f
RDX: 0000200000000300 RSI: 00007f85f870b0c0 RDI: 0000200000000300
RBP: 0000200000000300 R08: 00007ffc1f236920 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000073 R14: 00007f85f86e0033 R15: 00007ffc1f2367b0
 </TASK>
----------------
Code disassembly (best guess):
   0:	90                   	nop
   1:	0f 01 cb             	stac
   4:	0f ae e8             	lfence
   7:	0f b7 10             	movzwl (%rax),%edx
   a:	31 c0                	xor    %eax,%eax
   c:	0f 01 ca             	clac
   f:	c3                   	ret
  10:	90                   	nop
  11:	0f 01 cb             	stac
  14:	0f ae e8             	lfence
  17:	8b 10                	mov    (%rax),%edx
  19:	31 c0                	xor    %eax,%eax
  1b:	0f 01 ca             	clac
  1e:	c3                   	ret
  1f:	90                   	nop
  20:	90                   	nop
  21:	0f 01 cb             	stac
  24:	0f ae e8             	lfence
  27:	48 8b 10             	mov    (%rax),%rdx
* 2a:	31 c0                	xor    %eax,%eax <-- trapping instruction
  2c:	0f 01 ca             	clac
  2f:	c3                   	ret
  30:	90                   	nop
  31:	0f 01 ca             	clac
  34:	31 d2                	xor    %edx,%edx
  36:	48 c7 c0 f2 ff ff ff 	mov    $0xfffffffffffffff2,%rax
  3d:	c3                   	ret

Crashes (497):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/26 23:57 linux-5.15.y b9d57c40a767 9c2d0995 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/01/16 16:01 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2025/12/04 19:07 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2025/12/04 17:54 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/05 04:20 linux-5.15.y ef251c45f1cd a898ba9c .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/04 14:54 linux-5.15.y ef251c45f1cd 85f1bcf2 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/01/15 14:20 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/15 03:05 linux-5.15.y de8dfb3f0278 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/15 02:01 linux-5.15.y de8dfb3f0278 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/15 00:06 linux-5.15.y de8dfb3f0278 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/14 19:50 linux-5.15.y de8dfb3f0278 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/14 00:43 linux-5.15.y de8dfb3f0278 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/13 17:30 linux-5.15.y de8dfb3f0278 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/13 07:25 linux-5.15.y de8dfb3f0278 a0949470 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/13 03:14 linux-5.15.y de8dfb3f0278 a0949470 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/11 13:40 linux-5.15.y de8dfb3f0278 845acb1c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/11 03:42 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/11 00:02 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/10 18:33 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/10 18:08 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/10 08:49 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/10 05:24 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/09 23:31 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/09 16:51 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/09 11:49 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/09 06:03 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/08 10:28 linux-5.15.y ef251c45f1cd 5633175a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/07 01:59 linux-5.15.y ef251c45f1cd f250db59 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/06 15:08 linux-5.15.y ef251c45f1cd 1dddfd3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/06 04:47 linux-5.15.y ef251c45f1cd 26da2c66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/06 02:18 linux-5.15.y ef251c45f1cd 26da2c66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/05 23:59 linux-5.15.y ef251c45f1cd 26da2c66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/05 07:13 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/05 06:06 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/05 01:57 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/04 02:27 linux-5.15.y ef251c45f1cd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/03 20:48 linux-5.15.y ef251c45f1cd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/03 05:04 linux-5.15.y ef251c45f1cd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/03 01:49 linux-5.15.y ef251c45f1cd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/02 22:57 linux-5.15.y ef251c45f1cd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/02 00:39 linux-5.15.y ef251c45f1cd 753c55b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/01 18:15 linux-5.15.y ef251c45f1cd 753c55b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/01 15:32 linux-5.15.y ef251c45f1cd 753c55b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/01 05:40 linux-5.15.y ef251c45f1cd 753c55b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/05/01 00:51 linux-5.15.y ef251c45f1cd a7464baf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/30 00:41 linux-5.15.y b9d57c40a767 005438fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/27 16:32 linux-5.15.y b9d57c40a767 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/27 15:24 linux-5.15.y b9d57c40a767 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/26 22:57 linux-5.15.y b9d57c40a767 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/26 06:32 linux-5.15.y b9d57c40a767 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/25 19:50 linux-5.15.y b9d57c40a767 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/25 07:53 linux-5.15.y b9d57c40a767 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/24 22:42 linux-5.15.y b9d57c40a767 1c2b9291 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/24 21:00 linux-5.15.y b9d57c40a767 1c2b9291 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/24 10:08 linux-5.15.y b9d57c40a767 9cfb3ca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/23 18:42 linux-5.15.y b9d57c40a767 4c3406dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/23 14:59 linux-5.15.y b9d57c40a767 4c3406dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/23 10:27 linux-5.15.y b9d57c40a767 b10da5ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/22 08:41 linux-5.15.y b9d57c40a767 0b6ab7ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
2026/04/22 00:15 linux-5.15.y b9d57c40a767 0b6ab7ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf inconsistent lock state in trie_delete_elem
* Struck through repros no longer work on HEAD.