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: 207d, last: 15d
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 287d 661d 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 6207 2h22m 662d 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 3807 15h55m 661d 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 recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.930/6902 is trying to acquire lock:
ffff88802c855238 (&trie->lock){-.-.}-{2:2}, at: trie_delete_elem+0x96/0x6a0 kernel/bpf/lpm_trie.c:467

but task is already holding lock:
ffff88802c855a38 (&trie->lock){-.-.}-{2:2}, at: trie_delete_elem+0x96/0x6a0 kernel/bpf/lpm_trie.c:467

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

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

 *** DEADLOCK ***

 May be due to missing lock nesting notation

4 locks held by syz.0.930/6902:
 #0: ffff888023836e90 (&child->perf_event_mutex){+.+.}-{3:3}, at: perf_event_exit_task+0x95/0x870 kernel/events/core.c:13315
 #1: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #1: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #1: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: __bpf_trace_run kernel/trace/bpf_trace.c:2321 [inline]
 #1: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: bpf_trace_run2+0xde/0x3c0 kernel/trace/bpf_trace.c:2361
 #2: ffff88802c855a38 (&trie->lock){-.-.}-{2:2}, at: trie_delete_elem+0x96/0x6a0 kernel/bpf/lpm_trie.c:467
 #3: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #3: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #3: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: __bpf_trace_run kernel/trace/bpf_trace.c:2321 [inline]
 #3: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: bpf_trace_run2+0xde/0x3c0 kernel/trace/bpf_trace.c:2361

stack backtrace:
CPU: 1 PID: 6902 Comm: syz.0.930 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x5d40/0x7c80 kernel/locking/lockdep.c:5137
 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xa8/0xf0 kernel/locking/spinlock.c:162
 trie_delete_elem+0x96/0x6a0 kernel/bpf/lpm_trie.c:467
 bpf_prog_471848dd901c6738+0x4d/0x51
 bpf_dispatcher_nop_func include/linux/bpf.h:1224 [inline]
 __bpf_prog_run include/linux/filter.h:612 [inline]
 bpf_prog_run include/linux/filter.h:619 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:2322 [inline]
 bpf_trace_run2+0x1d1/0x3c0 kernel/trace/bpf_trace.c:2361
 __bpf_trace_contention_end+0xdd/0x130 include/trace/events/lock.h:122
 __traceiter_contention_end+0x78/0xb0 include/trace/events/lock.h:122
 trace_contention_end+0xe6/0x110 include/trace/events/lock.h:122
 __pv_queued_spin_lock_slowpath+0x7ec/0x9d0 kernel/locking/qspinlock.c:560
 pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:586 [inline]
 queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:51 [inline]
 queued_spin_lock include/asm-generic/qspinlock.h:114 [inline]
 do_raw_spin_lock+0x24e/0x2c0 kernel/locking/spinlock_debug.c:115
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:111 [inline]
 _raw_spin_lock_irqsave+0xb4/0xf0 kernel/locking/spinlock.c:162
 trie_delete_elem+0x96/0x6a0 kernel/bpf/lpm_trie.c:467
 bpf_prog_471848dd901c6738+0x4d/0x51
 bpf_dispatcher_nop_func include/linux/bpf.h:1224 [inline]
 __bpf_prog_run include/linux/filter.h:612 [inline]
 bpf_prog_run include/linux/filter.h:619 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:2322 [inline]
 bpf_trace_run2+0x1d1/0x3c0 kernel/trace/bpf_trace.c:2361
 __bpf_trace_contention_end+0xdd/0x130 include/trace/events/lock.h:122
 __traceiter_contention_end+0x78/0xb0 include/trace/events/lock.h:122
 trace_contention_end+0xc5/0xe0 include/trace/events/lock.h:122
 __mutex_lock_common kernel/locking/mutex.c:612 [inline]
 __mutex_lock+0x2fa/0xcc0 kernel/locking/mutex.c:747
 perf_event_exit_task+0x95/0x870 kernel/events/core.c:13315
 do_exit+0x889/0x23c0 kernel/exit.c:868
 do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
 __do_sys_exit_group kernel/exit.c:1035 [inline]
 __se_sys_exit_group kernel/exit.c:1033 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1033
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f864f78f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff2b4d0818 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f864f78f749
RDX: 0000000000000064 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007fff2b4d087c R08: 000000042b4d090f R09: 00000000000927c0
R10: 0000000000000001 R11: 0000000000000246 R12: 000000000000012e
R13: 00000000000927c0 R14: 0000000000018a98 R15: 00007fff2b4d08d0
 </TASK>

Crashes (215):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
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/09/14 01:28 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/13 04:54 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/13 03:42 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/11 06:27 linux-6.6.y fe9731e10004 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/09/10 02:44 linux-6.6.y fe9731e10004 fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in trie_delete_elem
2025/09/08 02:29 linux-6.6.y 355bd0b51d2f d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in trie_delete_elem
2025/09/08 01:21 linux-6.6.y 355bd0b51d2f d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf 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.