syzbot


possible deadlock in trie_delete_elem

Status: upstream: reported C repro on 2025/06/17 01:09
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+3293cebb61e068fec0e9@syzkaller.appspotmail.com
First crash: 333d, last: 5d05h
Fix commit to backport (bisect log) :
tree: upstream
commit cdc2e1d9d929d7f7009b3a5edca52388a2b0891f
Author: Nathan Chancellor <nathan@kernel.org>
Date: Mon Apr 14 22:00:59 2025 +0000

  lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP

  
Bug presence (2)
Date Name Commit Repro Result
2025/06/23 linux-6.6.y (ToT) 6282921b6825 C [report] possible deadlock in trie_delete_elem
2025/06/23 upstream (ToT) 86731a2a651e 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 412d 786d 28/29 fixed on 2025/06/16 12:34
linux-5.15 possible deadlock in trie_delete_elem missing-backport origin:upstream 4 C done 6264 10d 787d 0/3 upstream: reported C repro on 2024/03/19 12:09
linux-6.1 possible deadlock in trie_delete_elem origin:upstream missing-backport 4 C inconclusive 3819 115d 787d 0/3 upstream: reported C repro on 2024/03/20 00:33
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/08/29 12:39 9h43m fix candidate upstream OK (1) job log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
kworker/0:1/9 is trying to acquire lock:
ffff88807f4a4a38 (&trie->lock){-.-.}-{2:2}, at: trie_delete_elem+0x96/0x6a0 kernel/bpf/lpm_trie.c:467

but task is already holding lock:
ffff8880b8e37d68 (stock_lock){..-.}-{2:2}, at: local_lock_acquire include/linux/local_lock_internal.h:29 [inline]
ffff8880b8e37d68 (stock_lock){..-.}-{2:2}, at: refill_obj_stock+0xef/0x6a0 mm/memcontrol.c:3366

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (stock_lock){..-.}-{2:2}:
       local_lock_acquire include/linux/local_lock_internal.h:29 [inline]
       consume_obj_stock mm/memcontrol.c:3267 [inline]
       obj_cgroup_charge+0x10a/0x630 mm/memcontrol.c:3397
       memcg_slab_pre_alloc_hook mm/slab.h:508 [inline]
       slab_pre_alloc_hook+0x2e7/0x310 mm/slab.h:719
       slab_alloc_node mm/slub.c:3477 [inline]
       __kmem_cache_alloc_node+0x53/0x250 mm/slub.c:3534
       __do_kmalloc_node mm/slab_common.c:1006 [inline]
       __kmalloc_node+0xa4/0x230 mm/slab_common.c:1014
       kmalloc_node include/linux/slab.h:620 [inline]
       bpf_map_kmalloc_node+0xbc/0x1b0 kernel/bpf/syscall.c:424
       lpm_trie_node_alloc kernel/bpf/lpm_trie.c:291 [inline]
       trie_update_elem+0x169/0xea0 kernel/bpf/lpm_trie.c:338
       bpf_map_update_value+0x660/0x720 kernel/bpf/syscall.c:203
       generic_map_update_batch+0x5ec/0x810 kernel/bpf/syscall.c:1800
       bpf_map_do_batch+0x3d7/0x610 kernel/bpf/syscall.c:5010
       __sys_bpf+0x381/0x890 kernel/bpf/syscall.c:-1
       __do_sys_bpf kernel/bpf/syscall.c:5581 [inline]
       __se_sys_bpf kernel/bpf/syscall.c:5579 [inline]
       __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5579
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&trie->lock){-.-.}-{2:2}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3869 [inline]
       __lock_acquire+0x2df1/0x7d40 kernel/locking/lockdep.c:5137
       lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0xb4/0x100 kernel/locking/spinlock.c:162
       trie_delete_elem+0x96/0x6a0 kernel/bpf/lpm_trie.c:467
       bpf_prog_2c29ac5cdc6b1842+0x42/0x46
       bpf_dispatcher_nop_func include/linux/bpf.h:1224 [inline]
       __bpf_prog_run include/linux/filter.h:616 [inline]
       bpf_prog_run include/linux/filter.h:623 [inline]
       bpf_prog_run_array include/linux/bpf.h:1994 [inline]
       trace_call_bpf+0x333/0x6c0 kernel/trace/bpf_trace.c:143
       perf_trace_run_bpf_submit+0x7a/0x1c0 kernel/events/core.c:10295
       perf_trace_lock_acquire+0x34f/0x410 include/trace/events/lock.h:24
       trace_lock_acquire include/trace/events/lock.h:24 [inline]
       lock_acquire+0x3ef/0x420 kernel/locking/lockdep.c:5725
       rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
       rcu_read_lock include/linux/rcupdate.h:786 [inline]
       mod_objcg_mlstate+0xad/0x320 mm/memcontrol.c:2913
       drain_obj_stock+0x164/0x360 mm/memcontrol.c:3321
       refill_obj_stock+0x1fc/0x6a0 mm/memcontrol.c:3370
       memcg_slab_free_hook+0x125/0x1f0 mm/slab.h:576
       slab_free mm/slub.c:3825 [inline]
       kmem_cache_free_bulk+0x324/0x450 mm/slub.c:3948
       kfree_bulk include/linux/slab.h:517 [inline]
       kvfree_rcu_bulk+0x1eb/0x470 kernel/rcu/tree.c:3032
       kvfree_rcu_drain_ready kernel/rcu/tree.c:3216 [inline]
       kfree_rcu_monitor+0x7fe/0xf70 kernel/rcu/tree.c:3234
       process_one_work kernel/workqueue.c:2653 [inline]
       process_scheduled_works+0xa5d/0x15d0 kernel/workqueue.c:2730
       worker_thread+0xa55/0xfc0 kernel/workqueue.c:2811
       kthread+0x2fa/0x390 kernel/kthread.c:388
       ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
       ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293

other info that might help us debug this:

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

5 locks held by kworker/0:1/9:
 #0: ffff888017c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
 #0: ffff888017c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2730
 #1: ffffc900000e7d00 ((work_completion)(&(&krcp->monitor_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
 #1: ffffc900000e7d00 ((work_completion)(&(&krcp->monitor_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2730
 #2: ffffffff8d132200 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #2: ffffffff8d132200 (rcu_callback){....}-{0:0}, at: kvfree_rcu_bulk+0x135/0x470 kernel/rcu/tree.c:3026
 #3: ffff8880b8e37d68 (stock_lock){..-.}-{2:2}, at: local_lock_acquire include/linux/local_lock_internal.h:29 [inline]
 #3: ffff8880b8e37d68 (stock_lock){..-.}-{2:2}, at: refill_obj_stock+0xef/0x6a0 mm/memcontrol.c:3366
 #4: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #4: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #4: ffffffff8d1320e0 (rcu_read_lock){....}-{1:2}, at: trace_call_bpf+0xc3/0x6c0 kernel/trace/bpf_trace.c:142

stack backtrace:
CPU: 0 PID: 9 Comm: kworker/0:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: events kfree_rcu_monitor
Call Trace:
 <TASK>
 dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
 check_noncircular+0x2fc/0x400 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3869 [inline]
 __lock_acquire+0x2df1/0x7d40 kernel/locking/lockdep.c:5137
 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xb4/0x100 kernel/locking/spinlock.c:162
 trie_delete_elem+0x96/0x6a0 kernel/bpf/lpm_trie.c:467
 bpf_prog_2c29ac5cdc6b1842+0x42/0x46
 bpf_dispatcher_nop_func include/linux/bpf.h:1224 [inline]
 __bpf_prog_run include/linux/filter.h:616 [inline]
 bpf_prog_run include/linux/filter.h:623 [inline]
 bpf_prog_run_array include/linux/bpf.h:1994 [inline]
 trace_call_bpf+0x333/0x6c0 kernel/trace/bpf_trace.c:143
 perf_trace_run_bpf_submit+0x7a/0x1c0 kernel/events/core.c:10295
 perf_trace_lock_acquire+0x34f/0x410 include/trace/events/lock.h:24
 trace_lock_acquire include/trace/events/lock.h:24 [inline]
 lock_acquire+0x3ef/0x420 kernel/locking/lockdep.c:5725
 rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 rcu_read_lock include/linux/rcupdate.h:786 [inline]
 mod_objcg_mlstate+0xad/0x320 mm/memcontrol.c:2913
 drain_obj_stock+0x164/0x360 mm/memcontrol.c:3321
 refill_obj_stock+0x1fc/0x6a0 mm/memcontrol.c:3370
 memcg_slab_free_hook+0x125/0x1f0 mm/slab.h:576
 slab_free mm/slub.c:3825 [inline]
 kmem_cache_free_bulk+0x324/0x450 mm/slub.c:3948
 kfree_bulk include/linux/slab.h:517 [inline]
 kvfree_rcu_bulk+0x1eb/0x470 kernel/rcu/tree.c:3032
 kvfree_rcu_drain_ready kernel/rcu/tree.c:3216 [inline]
 kfree_rcu_monitor+0x7fe/0xf70 kernel/rcu/tree.c:3234
 process_one_work kernel/workqueue.c:2653 [inline]
 process_scheduled_works+0xa5d/0x15d0 kernel/workqueue.c:2730
 worker_thread+0xa55/0xfc0 kernel/workqueue.c:2811
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>

Crashes (223):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/05/03 15:19 linux-6.6.y 258cf62a6dfd a0d91488 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/12/12 20:24 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/12/09 17:52 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/08 06:44 linux-6.6.y 0a805b6ea8cd 4e1406b4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/07 10:37 linux-6.6.y 0a805b6ea8cd 4e1406b4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/31 19:18 linux-6.6.y e5bbb12db2c7 2c50b6a9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/26 22:00 linux-6.6.y 4a243110dc88 c0460fcd .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/10 07:46 linux-6.6.y e617101e5626 ff1712fe .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/06 22:37 linux-6.6.y e617101e5626 91305dbe .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/09/27 10:29 linux-6.6.y 147338df3487 001c9061 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/09/14 12:09 linux-6.6.y 60a9e718726f e2beed91 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/08/02 07:04 linux-6.6.y 3a8ababb8b6a 7368264b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/07/26 20:30 linux-6.6.y dbcb8d8e4163 fb8f743d .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/06/17 12:08 linux-6.6.y c2603c511feb cfebc887 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2026/05/10 23:18 linux-6.6.y 3b9f64db0496 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2026/05/03 13:02 linux-6.6.y 258cf62a6dfd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2026/01/21 15:46 linux-6.6.y cbb31f77b879 6f1aa2f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2026/01/18 02:50 linux-6.6.y cbb31f77b879 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2026/01/12 06:28 linux-6.6.y c596736dadab d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/12/26 08:55 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/12/21 21:41 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/12/13 20:51 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/12/12 16:14 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/27 02:15 linux-6.6.y 1e89a1be4fe9 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/11/26 11:32 linux-6.6.y 1e89a1be4fe9 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/11/26 08:15 linux-6.6.y 1e89a1be4fe9 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/24 09:00 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/18 21:23 linux-6.6.y 0a805b6ea8cd ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/17 15:01 linux-6.6.y 0a805b6ea8cd ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/16 05:43 linux-6.6.y 0a805b6ea8cd f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/15 19:42 linux-6.6.y 0a805b6ea8cd f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/13 07:28 linux-6.6.y 0a805b6ea8cd 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/06 22:46 linux-6.6.y 0a805b6ea8cd 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/06 19:17 linux-6.6.y 0a805b6ea8cd 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/11/06 15:00 linux-6.6.y 0a805b6ea8cd a6c9c731 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/22 17:16 linux-6.6.y f231f248323d 252fbbad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/10/22 17:16 linux-6.6.y f231f248323d 252fbbad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/10/22 08:54 linux-6.6.y f231f248323d 252fbbad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/21 20:19 linux-6.6.y f231f248323d 9832ed61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/10/19 09:53 linux-6.6.y 0bbbd97a442d 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/15 22:14 linux-6.6.y 0bbbd97a442d 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/15 14:07 linux-6.6.y 0bbbd97a442d b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/14 21:21 linux-6.6.y 655054d2c3c1 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/11 09:48 linux-6.6.y e617101e5626 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/10/09 05:34 linux-6.6.y e617101e5626 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/08 16:34 linux-6.6.y e617101e5626 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/10/08 12:58 linux-6.6.y e617101e5626 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/08 09:53 linux-6.6.y e617101e5626 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/10/08 00:47 linux-6.6.y e617101e5626 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/03 20:35 linux-6.6.y f34f16e5c632 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/10/03 00:37 linux-6.6.y f34f16e5c632 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/10/01 07:46 linux-6.6.y 147338df3487 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/09/24 17:25 linux-6.6.y af1544b5d072 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/09/18 08:03 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/09/14 14:06 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/09/14 08:16 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/09/14 01:34 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/06/17 01:08 linux-6.6.y c2603c511feb d1716036 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
* Struck through repros no longer work on HEAD.