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: 521d, last: 11h11m
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 146d 520d 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 3701 1d07h 521d 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 106 2d09h 67d 0/2 upstream: reported C repro on 2025/06/17 01:09
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
5.15.189-syzkaller #0 Not tainted
------------------------------------------------------
udevd/3562 is trying to acquire lock:
ffff8880796e9db8 (&trie->lock){....}-{2:2}, at: trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467

but task is already holding lock:
ffff8880b912a218 (hrtimer_bases.lock){-.-.}-{2:2}, at: lock_hrtimer_base kernel/time/hrtimer.c:168 [inline]
ffff8880b912a218 (hrtimer_bases.lock){-.-.}-{2:2}, at: hrtimer_start_range_ns+0xff/0xc20 kernel/time/hrtimer.c:1289

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (hrtimer_bases.lock){-.-.}-{2:2}:
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
       lock_hrtimer_base kernel/time/hrtimer.c:168 [inline]
       hrtimer_start_range_ns+0xff/0xc20 kernel/time/hrtimer.c:1289
       hrtimer_start include/linux/hrtimer.h:420 [inline]
       run_page_cache_worker kernel/rcu/tree.c:3492 [inline]
       kvfree_call_rcu+0x60d/0x7c0 kernel/rcu/tree.c:3603
       rtnl_register_internal+0x44e/0x540 net/core/rtnetlink.c:223
       rtnl_register+0x2e/0x70 net/core/rtnetlink.c:273
       ip_rt_init+0x2e0/0x3a0 net/ipv4/route.c:3795
       ip_init+0xa/0x20 net/ipv4/ip_output.c:1749
       inet_init+0x28b/0x3a0 net/ipv4/af_inet.c:2007
       do_one_initcall+0x1ee/0x680 init/main.c:1302
       do_initcall_level+0x137/0x1f0 init/main.c:1375
       do_initcalls+0x4b/0x90 init/main.c:1391
       kernel_init_freeable+0x3ce/0x560 init/main.c:1615
       kernel_init+0x19/0x1b0 init/main.c:1506
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

-> #1 (krc.lock){..-.}-{2:2}:
       __raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
       _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
       krc_this_cpu_lock kernel/rcu/tree.c:3203 [inline]
       add_ptr_to_bulk_krc_lock kernel/rcu/tree.c:3510 [inline]
       kvfree_call_rcu+0x186/0x7c0 kernel/rcu/tree.c:3601
       trie_delete_elem+0x58c/0x710 kernel/bpf/lpm_trie.c:-1
       0xffffffffa001a8ce
       bpf_dispatcher_nop_func include/linux/bpf.h:790 [inline]
       __bpf_prog_run include/linux/filter.h:628 [inline]
       bpf_prog_run include/linux/filter.h:635 [inline]
       __bpf_trace_run kernel/trace/bpf_trace.c:1878 [inline]
       bpf_trace_run2+0x15b/0x2d0 kernel/trace/bpf_trace.c:1915
       __bpf_trace_sys_enter+0x60/0x70 include/trace/events/syscalls.h:18
       trace_sys_enter+0x65/0x80 include/trace/events/syscalls.h:18
       syscall_trace_enter+0x115/0x180 kernel/entry/common.c:77
       do_syscall_64+0x24/0xa0 arch/x86/entry/common.c:76
       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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
       trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467
       bpf_prog_2c29ac5cdc6b1842+0x3a/0x4cc
       bpf_dispatcher_nop_func include/linux/bpf.h:790 [inline]
       __bpf_prog_run include/linux/filter.h:628 [inline]
       bpf_prog_run include/linux/filter.h:635 [inline]
       __bpf_trace_run kernel/trace/bpf_trace.c:1878 [inline]
       bpf_trace_run2+0x15b/0x2d0 kernel/trace/bpf_trace.c:1915
       trace_hrtimer_start include/trace/events/timer.h:199 [inline]
       debug_activate kernel/time/hrtimer.c:466 [inline]
       enqueue_hrtimer+0x314/0x370 kernel/time/hrtimer.c:1074
       __hrtimer_start_range_ns kernel/time/hrtimer.c:1249 [inline]
       hrtimer_start_range_ns+0xa7e/0xc20 kernel/time/hrtimer.c:1291
       hrtimer_start_expires include/linux/hrtimer.h:434 [inline]
       hrtimer_sleeper_start_expires kernel/time/hrtimer.c:1970 [inline]
       schedule_hrtimeout_range_clock+0x3a4/0x560 kernel/time/hrtimer.c:2318
       ep_poll+0x1739/0x19a0 fs/eventpoll.c:1918
       do_epoll_wait+0x1a1/0x210 fs/eventpoll.c:2296
       __do_sys_epoll_wait fs/eventpoll.c:2308 [inline]
       __se_sys_epoll_wait fs/eventpoll.c:2303 [inline]
       __x64_sys_epoll_wait+0x1bb/0x200 fs/eventpoll.c:2303
       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:

Chain exists of:
  &trie->lock --> krc.lock --> hrtimer_bases.lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(hrtimer_bases.lock);
                               lock(krc.lock);
                               lock(hrtimer_bases.lock);
  lock(&trie->lock);

 *** DEADLOCK ***

2 locks held by udevd/3562:
 #0: ffff8880b912a218 (hrtimer_bases.lock){-.-.}-{2:2}, at: lock_hrtimer_base kernel/time/hrtimer.c:168 [inline]
 #0: ffff8880b912a218 (hrtimer_bases.lock){-.-.}-{2:2}, at: hrtimer_start_range_ns+0xff/0xc20 kernel/time/hrtimer.c:1289
 #1: ffffffff8c11c360 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:311

stack backtrace:
CPU: 1 PID: 3562 Comm: udevd Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
 trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467
 bpf_prog_2c29ac5cdc6b1842+0x3a/0x4cc
 bpf_dispatcher_nop_func include/linux/bpf.h:790 [inline]
 __bpf_prog_run include/linux/filter.h:628 [inline]
 bpf_prog_run include/linux/filter.h:635 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:1878 [inline]
 bpf_trace_run2+0x15b/0x2d0 kernel/trace/bpf_trace.c:1915
 trace_hrtimer_start include/trace/events/timer.h:199 [inline]
 debug_activate kernel/time/hrtimer.c:466 [inline]
 enqueue_hrtimer+0x314/0x370 kernel/time/hrtimer.c:1074
 __hrtimer_start_range_ns kernel/time/hrtimer.c:1249 [inline]
 hrtimer_start_range_ns+0xa7e/0xc20 kernel/time/hrtimer.c:1291
 hrtimer_start_expires include/linux/hrtimer.h:434 [inline]
 hrtimer_sleeper_start_expires kernel/time/hrtimer.c:1970 [inline]
 schedule_hrtimeout_range_clock+0x3a4/0x560 kernel/time/hrtimer.c:2318
 ep_poll+0x1739/0x19a0 fs/eventpoll.c:1918
 do_epoll_wait+0x1a1/0x210 fs/eventpoll.c:2296
 __do_sys_epoll_wait fs/eventpoll.c:2308 [inline]
 __se_sys_epoll_wait fs/eventpoll.c:2303 [inline]
 __x64_sys_epoll_wait+0x1bb/0x200 fs/eventpoll.c:2303
 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:0x7fb23845e407
Code: 48 89 fa 4c 89 df e8 38 aa 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff
RSP: 002b:00007fffa6a4e030 EFLAGS: 00000202 ORIG_RAX: 00000000000000e8
RAX: ffffffffffffffda RBX: 00007fb238370880 RCX: 00007fb23845e407
RDX: 0000000000000008 RSI: 00007fffa6a4e190 RDI: 000000000000000b
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000bb8 R11: 0000000000000202 R12: 0000000000000000
R13: 000055a325c09100 R14: 0000000000000000 R15: 00007fffa6a4e280
 </TASK>

Crashes (5293):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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/09/21 12:55 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/09/16 12:18 linux-5.15.y 3a5928702e71 08d8a733 .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/01 02:11 linux-5.15.y fa93fa65db6e 1eda0d14 .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/06/08 15:42 linux-5.15.y c61bd26ae81a 82c05ab8 .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/05/14 21:09 linux-5.15.y 284087d4f7d5 fdb4c10c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/04/26 08:21 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/04/26 04:09 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/04/24 10:55 linux-5.15.y c52b9710c83d 21339d7b .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/04/18 16:16 linux-5.15.y c52b9710c83d af24b050 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/04/06 06:50 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/04/05 16:14 linux-5.15.y 9465fef4ae35 77230c29 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/04/05 11:36 linux-5.15.y 9465fef4ae35 0ee3535e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2024/04/01 16:34 linux-5.15.y 9465fef4ae35 6baf5069 .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 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
2025/08/22 15:39 linux-5.15.y c79648372d02 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/21 22:59 linux-5.15.y c79648372d02 3e79b825 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/21 21:57 linux-5.15.y c79648372d02 3e79b825 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/21 16:22 linux-5.15.y c79648372d02 3e79b825 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/20 16:22 linux-5.15.y c79648372d02 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/20 13:16 linux-5.15.y c79648372d02 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/20 13:15 linux-5.15.y c79648372d02 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/20 08:26 linux-5.15.y c79648372d02 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/19 23:05 linux-5.15.y c79648372d02 254a27c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/19 17:59 linux-5.15.y c79648372d02 254a27c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/19 15:24 linux-5.15.y c79648372d02 254a27c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/19 13:37 linux-5.15.y c79648372d02 254a27c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/18 19:39 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/18 07:17 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/17 22:13 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/17 17:15 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/17 10:20 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/17 08:50 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/16 13:48 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/16 12:17 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/16 10:14 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/15 02:54 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/14 23:18 linux-5.15.y c79648372d02 5d8c2ac2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/14 13:43 linux-5.15.y c79648372d02 5d8c2ac2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/14 05:02 linux-5.15.y c79648372d02 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/14 03:13 linux-5.15.y c79648372d02 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/13 03:10 linux-5.15.y c79648372d02 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/13 01:58 linux-5.15.y c79648372d02 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/12 21:30 linux-5.15.y c79648372d02 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/12 18:46 linux-5.15.y c79648372d02 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/12 06:18 linux-5.15.y c79648372d02 c06e8995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/11 18:59 linux-5.15.y c79648372d02 c06e8995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/11 03:37 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/10 04:56 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/10 02:38 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/10 00:47 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/09 23:13 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/09 03:01 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/08 23:51 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/08 18:19 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/08 11:01 linux-5.15.y c79648372d02 6a893178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in trie_delete_elem
2025/08/08 04:43 linux-5.15.y c79648372d02 6a893178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/08 03:39 linux-5.15.y c79648372d02 6a893178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf possible deadlock in trie_delete_elem
2025/08/08 02:12 linux-5.15.y c79648372d02 6a893178 .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.