syzbot


possible deadlock in trie_delete_elem

Status: upstream: reported C repro on 2024/03/19 12:09
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+c361763297bd80b2cc11@syzkaller.appspotmail.com
First crash: 808d, last: 3d13h
Fix commit to backport (bisect log) :
tree: upstream
commit 3d8dc43eb2a3d179809f5fc27c88c93a57ea123d
Author: Hou Tao <houtao1@huawei.com>
Date: Fri Dec 6 11:06:19 2024 +0000

  bpf: Switch to bpf mem allocator for LPM trie

  
Bug presence (3)
Date Name Commit Repro Result
2024/12/22 linux-5.15.y (ToT) 91786f140358 C [report] possible deadlock in trie_delete_elem
2024/05/03 upstream (ToT) 3d25a941ea50 C [report] possible deadlock in trie_delete_elem
2024/12/22 upstream (ToT) 48f506ad0b68 C Didn't crash
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in trie_delete_elem bpf 4 C done done 21444 433d 808d 28/29 fixed on 2025/06/16 12:34
linux-6.1 possible deadlock in trie_delete_elem origin:upstream missing-backport 4 C inconclusive 3819 136d 808d 0/3 upstream: reported C repro on 2024/03/20 00:33
linux-6.6 possible deadlock in trie_delete_elem origin:lts-only 4 C done 223 26d 354d 0/2 upstream: reported C repro on 2025/06/17 01:09
Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/05/06 02:29 16m retest repro linux-5.15.y report log
2026/05/06 02:29 15m retest repro linux-5.15.y report log
2026/05/06 02:29 18m retest repro linux-5.15.y report log
2026/05/06 02:29 15m retest repro linux-5.15.y report log
2026/05/06 02:29 15m retest repro linux-5.15.y report log
2026/04/16 22:01 11m retest repro linux-5.15.y report log
2026/04/16 22:01 11m retest repro linux-5.15.y report log
2026/04/16 22:01 11m retest repro linux-5.15.y report log
2026/04/16 22:01 12m retest repro linux-5.15.y report log
2026/04/16 22:01 12m retest repro linux-5.15.y report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/01/08 23:56 7h14m fix candidate upstream OK (1) job log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/4482 is trying to acquire lock:
ffff888020b90a38 (&trie->lock){..-.}-{2:2}, at: trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467

but task is already holding lock:
ffffffff8c9375d8 (depot_lock){-.-.}-{2:2}, at: stack_depot_save+0x1d2/0x440 lib/stackdepot.c:307

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (depot_lock){-.-.}-{2:2}:
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0xb0/0x100 kernel/locking/spinlock.c:162
       stack_depot_save+0x1d2/0x440 lib/stackdepot.c:307
       kasan_save_stack mm/kasan/common.c:40 [inline]
       kasan_set_track mm/kasan/common.c:46 [inline]
       set_alloc_info mm/kasan/common.c:434 [inline]
       ____kasan_kmalloc mm/kasan/common.c:513 [inline]
       __kasan_kmalloc+0xcc/0xf0 mm/kasan/common.c:522
       kmalloc_node include/linux/slab.h:630 [inline]
       bpf_map_kmalloc_node+0xba/0x140 kernel/bpf/syscall.c:432
       lpm_trie_node_alloc kernel/bpf/lpm_trie.c:290 [inline]
       trie_update_elem+0x1cc/0xc50 kernel/bpf/lpm_trie.c:332
       bpf_map_update_value+0x57d/0x650 kernel/bpf/syscall.c:223
       generic_map_update_batch+0x52d/0x7d0 kernel/bpf/syscall.c:1430
       bpf_map_do_batch+0x466/0x600 kernel/bpf/syscall.c:-1
       __sys_bpf+0x671/0x6f0 kernel/bpf/syscall.c:-1
       __do_sys_bpf kernel/bpf/syscall.c:4761 [inline]
       __se_sys_bpf kernel/bpf/syscall.c:4759 [inline]
       __x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4759
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&trie->lock){..-.}-{2:2}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012
       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
       bpf_prog_2c29ac5cdc6b1842+0x3a/0x1e8
       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_PROG_RUN_ARRAY include/linux/bpf.h:1439 [inline]
       trace_call_bpf+0x2b1/0x5b0 kernel/trace/bpf_trace.c:127
       perf_trace_run_bpf_submit+0x79/0x1c0 kernel/events/core.c:10016
       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
       __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:158 [inline]
       _raw_spin_unlock_irqrestore+0x6d/0x120 kernel/locking/spinlock.c:194
       stack_depot_save+0x404/0x440 lib/stackdepot.c:331
       kasan_save_stack+0x4b/0x60 mm/kasan/common.c:40
       kasan_record_aux_stack+0xb8/0x100 mm/kasan/generic.c:348
       task_work_add+0x2f/0x1d0 kernel/task_work.c:38
       fput_many+0xde/0x1a0 fs/file_table.c:367
       filp_close+0x10e/0x150 fs/open.c:1371
       __range_close fs/file.c:692 [inline]
       __close_range+0x24f/0x510 fs/file.c:747
       __do_sys_close_range fs/open.c:1410 [inline]
       __se_sys_close_range fs/open.c:1407 [inline]
       __x64_sys_close_range+0x76/0x80 fs/open.c:1407
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(depot_lock);
                               lock(&trie->lock);
                               lock(depot_lock);
  lock(&trie->lock);

 *** DEADLOCK ***

2 locks held by syz.0.17/4482:
 #0: ffffffff8c9375d8 (depot_lock){-.-.}-{2:2}, at: stack_depot_save+0x1d2/0x440 lib/stackdepot.c:307
 #1: ffffffff8c31f320 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:312

stack backtrace:
CPU: 1 PID: 4482 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012
 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
 bpf_prog_2c29ac5cdc6b1842+0x3a/0x1e8
 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_PROG_RUN_ARRAY include/linux/bpf.h:1439 [inline]
 trace_call_bpf+0x2b1/0x5b0 kernel/trace/bpf_trace.c:127
 perf_trace_run_bpf_submit+0x79/0x1c0 kernel/events/core.c:10016
 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
 __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:158 [inline]
 _raw_spin_unlock_irqrestore+0x6d/0x120 kernel/locking/spinlock.c:194
 stack_depot_save+0x404/0x440 lib/stackdepot.c:331
 kasan_save_stack+0x4b/0x60 mm/kasan/common.c:40
 kasan_record_aux_stack+0xb8/0x100 mm/kasan/generic.c:348
 task_work_add+0x2f/0x1d0 kernel/task_work.c:38
 fput_many+0xde/0x1a0 fs/file_table.c:367
 filp_close+0x10e/0x150 fs/open.c:1371
 __range_close fs/file.c:692 [inline]
 __close_range+0x24f/0x510 fs/file.c:747
 __do_sys_close_range fs/open.c:1410 [inline]
 __se_sys_close_range fs/open.c:1407 [inline]
 __x64_sys_close_range+0x76/0x80 fs/open.c:1407
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f5dda21ee59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc69253eb8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: ffffffffffffffda RBX: 00007ffc69253fa0 RCX: 00007f5dda21ee59
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 0000000000012de4 R08: 0000000000000001 R09: 0000000000000000
R10: 0000001b2cd20000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5dda497fac R14: 00007f5dda497fa8 R15: 00007f5dda497fa0
 </TASK>

Crashes (6269):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/05/23 23:05 linux-5.15.y 241d66fa280c c69befb3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/11/14 19:18 linux-5.15.y cc5ec8769306 f7988ea4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/11/06 01:35 linux-5.15.y cc5ec8769306 a6c9c731 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/11/05 00:19 linux-5.15.y cc5ec8769306 686bf657 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/10/26 20:25 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/10/26 15:14 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/10/26 10:23 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/10/25 17:34 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/10/25 14:15 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/10/25 12:39 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/10/25 11:35 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/10/24 15:52 linux-5.15.y ac56c046adf4 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/09/26 15:29 linux-5.15.y 43bb85222e53 0abd0691 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/26 09:04 linux-5.15.y c79648372d02 bf27483f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/03 20:38 linux-5.15.y c79648372d02 7368264b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/07/23 19:24 linux-5.15.y c79648372d02 e1dd4f22 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/07/23 11:08 linux-5.15.y c79648372d02 e1dd4f22 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/07/23 05:20 linux-5.15.y c79648372d02 e1dd4f22 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/07/23 00:49 linux-5.15.y c79648372d02 8e9d1dc1 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/07/22 21:49 linux-5.15.y c79648372d02 8e9d1dc1 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/07/18 07:22 linux-5.15.y c79648372d02 88248e14 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/06/24 03:29 linux-5.15.y 1c700860e8bc e2f27c35 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/06/20 19:53 linux-5.15.y 1c700860e8bc 804b3919 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/05/22 22:53 linux-5.15.y 98f47d0e9b8c 0919b50b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/04/20 20:23 linux-5.15.y f7347f400572 2a20f901 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/04/12 21:46 linux-5.15.y f7347f400572 0bd6db41 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/04/11 08:55 linux-5.15.y f7347f400572 94486846 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/04/02 04:08 linux-5.15.y 0c935c049b5c b8645499 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/02/17 03:56 linux-5.15.y c16c81c81336 40a34ec9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/02/03 03:44 linux-5.15.y c16c81c81336 568559e4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/02/02 22:25 linux-5.15.y c16c81c81336 568559e4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/01/20 06:48 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/01/18 13:18 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/01/18 12:37 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/01/11 22:23 linux-5.15.y 4735586da88e 6dbc6a9b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/01/07 21:05 linux-5.15.y 91786f140358 f3558dbf .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/01/01 16:55 linux-5.15.y 91786f140358 d3ccff63 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/01/01 12:38 linux-5.15.y 91786f140358 d3ccff63 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/10/12 22:31 linux-5.15.y 3a5928702e71 084d8178 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/09/22 17:34 linux-5.15.y 3a5928702e71 6f888b75 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/03/20 02:06 linux-5.15.y b95c01af2113 e104824c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/03/20 01:06 linux-5.15.y b95c01af2113 e104824c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/01/11 11:15 linux-5.15.y 4735586da88e 6dbc6a9b .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/06/02 20:43 linux-5.15.y dc027a595035 62fe1528 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/05/25 02:47 linux-5.15.y 241d66fa280c c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/05/24 03:57 linux-5.15.y 241d66fa280c c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/05/23 22:18 linux-5.15.y 241d66fa280c c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/21 23:17 linux-5.15.y 9eec9a14ee10 8fc37797 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/21 22:22 linux-5.15.y 9eec9a14ee10 8fc37797 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/21 07:33 linux-5.15.y 9eec9a14ee10 6f1aa2f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/21 05:37 linux-5.15.y 9eec9a14ee10 6f1aa2f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/20 01:13 linux-5.15.y 9eec9a14ee10 572effc1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/19 23:32 linux-5.15.y 9eec9a14ee10 572effc1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/19 12:25 linux-5.15.y 68efe5a6c16a a9fc5226 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/19 10:03 linux-5.15.y 68efe5a6c16a a9fc5226 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/19 02:45 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/18 22:16 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/18 10:33 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/18 09:29 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/18 09:26 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/18 05:08 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/14 16:55 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/12 08:03 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2026/01/11 09:01 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/10 23:35 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/10 18:33 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/10 14:25 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/10 10:54 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/10 05:38 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2026/01/10 03:44 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/09 05:40 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/09 05:15 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/08 01:35 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2026/01/04 09:25 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2026/01/02 22:18 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2026/01/01 05:16 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/30 14:33 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/29 22:55 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/12/29 13:31 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/28 19:24 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/28 14:47 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/12/28 12:29 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/27 09:06 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/12/27 09:06 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/12/26 15:35 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/26 07:58 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/12/26 04:16 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/25 16:57 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/24 23:21 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/12/24 10:49 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/03/19 12:09 linux-5.15.y b95c01af2113 e104824c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
* Struck through repros no longer work on HEAD.