syzbot


possible deadlock in __bpf_ringbuf_reserve (2)

Status: upstream: reported C repro on 2025/08/25 17:39
Subsystems: bpf
[Documentation on labels]
Reported-by: syzbot+fa5c2814795b5adca240@syzkaller.appspotmail.com
First crash: 47d, last: 31d
Cause bisection: introduced by (bisect log) :
commit 27861fc720be2c39b861d8bdfb68287f54de6855
Author: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Date: Thu Aug 21 16:26:00 2025 +0000

  bpf: Drop rqspinlock usage in ringbuf

Crash: possible deadlock in __bpf_ringbuf_reserve (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [bpf?] possible deadlock in __bpf_ringbuf_reserve (2) 3 (5) 2025/09/01 22:10
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in __bpf_ringbuf_reserve origin:upstream missing-backport 4 C inconclusive 79 4d02h 581d 0/3 upstream: reported C repro on 2024/03/08 23:13
linux-5.15 possible deadlock in __bpf_ringbuf_reserve 4 1 36d 36d 0/3 upstream: reported on 2025/09/04 22:27
linux-6.6 possible deadlock in __bpf_ringbuf_reserve origin:lts-only 4 C 20 15d 99d 0/2 upstream: reported C repro on 2025/07/04 03:51
upstream possible deadlock in __bpf_ringbuf_reserve bpf 4 C error 2490 172d 577d 28/29 fixed on 2025/06/10 16:19
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/09/23 22:01 33m retest repro bpf OK log
2025/09/23 14:53 24m retest repro bpf OK log
2025/09/23 14:53 24m retest repro bpf OK log
2025/09/23 14:53 26m retest repro bpf OK log
2025/09/23 14:53 40m retest repro bpf OK log
2025/09/23 14:53 40m retest repro bpf OK log
2025/09/23 12:22 24m retest repro bpf OK log
2025/09/23 12:22 25m retest repro bpf OK log
2025/09/23 12:22 24m retest repro bpf OK log
2025/09/23 12:22 24m retest repro bpf OK log
Cause bisection attempts (2)
Created Duration User Patch Repo Result
2025/09/01 10:45 11h23m bisect bpf OK (1) job log log
2025/08/24 21:04 6h05m bisect bpf error job log

Sample crash report:
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
ksoftirqd/1/23 is trying to acquire lock:
ffffc90019a010d8 (&rb->spinlock){-.-.}-{2:2}, at: __bpf_ringbuf_reserve+0x1c7/0x5a0 kernel/bpf/ringbuf.c:423

but task is already holding lock:
ffffc9000bb4a0d8 (&rb->spinlock){-.-.}-{2:2}, at: __bpf_ringbuf_reserve+0x1c7/0x5a0 kernel/bpf/ringbuf.c:423

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

       CPU0
       ----
  lock(&rb->spinlock);
  lock(&rb->spinlock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

4 locks held by ksoftirqd/1/23:
 #0: ffffffff8e139fc0 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e139fc0 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2599 [inline]
 #0: ffffffff8e139fc0 (rcu_callback){....}-{0:0}, at: rcu_core+0xc37/0x1770 kernel/rcu/tree.c:2861
 #1: ffffffff8e139ea0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #1: ffffffff8e139ea0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #1: ffffffff8e139ea0 (rcu_read_lock){....}-{1:3}, at: __bpf_trace_run kernel/trace/bpf_trace.c:2256 [inline]
 #1: ffffffff8e139ea0 (rcu_read_lock){....}-{1:3}, at: bpf_trace_run2+0x186/0x4b0 kernel/trace/bpf_trace.c:2298
 #2: ffffc9000bb4a0d8 (&rb->spinlock){-.-.}-{2:2}, at: __bpf_ringbuf_reserve+0x1c7/0x5a0 kernel/bpf/ringbuf.c:423
 #3: ffffffff8e139ea0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #3: ffffffff8e139ea0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #3: ffffffff8e139ea0 (rcu_read_lock){....}-{1:3}, at: trace_call_bpf+0xb7/0x850 kernel/trace/bpf_trace.c:-1

stack backtrace:
CPU: 1 UID: 0 PID: 23 Comm: ksoftirqd/1 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_deadlock_bug+0x28b/0x2a0 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain+0x1a3f/0x2140 kernel/locking/lockdep.c:3895
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xa7/0xf0 kernel/locking/spinlock.c:162
 __bpf_ringbuf_reserve+0x1c7/0x5a0 kernel/bpf/ringbuf.c:423
 ____bpf_ringbuf_reserve kernel/bpf/ringbuf.c:474 [inline]
 bpf_ringbuf_reserve+0x5c/0x70 kernel/bpf/ringbuf.c:466
 bpf_prog_df2ea1bb7efca089+0x36/0x54
 bpf_dispatcher_nop_func include/linux/bpf.h:1332 [inline]
 __bpf_prog_run include/linux/filter.h:718 [inline]
 bpf_prog_run include/linux/filter.h:725 [inline]
 bpf_prog_run_array include/linux/bpf.h:2292 [inline]
 trace_call_bpf+0x326/0x850 kernel/trace/bpf_trace.c:146
 perf_trace_run_bpf_submit+0x78/0x170 kernel/events/core.c:10911
 do_perf_trace_contention_end include/trace/events/lock.h:122 [inline]
 perf_trace_contention_end+0x253/0x2f0 include/trace/events/lock.h:122
 __do_trace_contention_end include/trace/events/lock.h:122 [inline]
 trace_contention_end+0x111/0x140 include/trace/events/lock.h:122
 __pv_queued_spin_lock_slowpath+0x9f9/0xb60 kernel/locking/qspinlock.c:374
 pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:557 [inline]
 queued_spin_lock_slowpath+0x43/0x50 arch/x86/include/asm/qspinlock.h:51
 queued_spin_lock include/asm-generic/qspinlock.h:114 [inline]
 do_raw_spin_lock+0x21f/0x290 kernel/locking/spinlock_debug.c:116
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:111 [inline]
 _raw_spin_lock_irqsave+0xb3/0xf0 kernel/locking/spinlock.c:162
 __bpf_ringbuf_reserve+0x1c7/0x5a0 kernel/bpf/ringbuf.c:423
 ____bpf_ringbuf_reserve kernel/bpf/ringbuf.c:474 [inline]
 bpf_ringbuf_reserve+0x5c/0x70 kernel/bpf/ringbuf.c:466
 bpf_prog_1b7a58cee4f01415+0x2e/0x4f
 bpf_dispatcher_nop_func include/linux/bpf.h:1332 [inline]
 __bpf_prog_run include/linux/filter.h:718 [inline]
 bpf_prog_run include/linux/filter.h:725 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:2257 [inline]
 bpf_trace_run2+0x281/0x4b0 kernel/trace/bpf_trace.c:2298
 __do_trace_kfree include/trace/events/kmem.h:94 [inline]
 trace_kfree include/trace/events/kmem.h:94 [inline]
 kfree+0x3a0/0x440 mm/slub.c:4866
 slab_free_after_rcu_debug+0x60/0x2a0 mm/slub.c:4717
 rcu_do_batch kernel/rcu/tree.c:2605 [inline]
 rcu_core+0xcab/0x1770 kernel/rcu/tree.c:2861
 handle_softirqs+0x283/0x870 kernel/softirq.c:579
 run_ksoftirqd+0x9b/0x100 kernel/softirq.c:968
 smpboot_thread_fn+0x542/0xa60 kernel/smpboot.c:160
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (22):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/09 12:06 bpf 71ca59e23445 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/09/08 22:12 bpf 71ca59e23445 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/09/07 01:20 bpf 71ca59e23445 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/09/01 20:53 bpf 71ca59e23445 807a3b61 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/09/01 16:36 bpf 71ca59e23445 807a3b61 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/09/01 14:58 bpf 71ca59e23445 807a3b61 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/09/01 12:31 bpf 71ca59e23445 807a3b61 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/09/01 10:52 bpf 71ca59e23445 807a3b61 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/31 19:03 bpf 71ca59e23445 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/29 17:29 bpf 27861fc720be 3e1beec6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/28 14:29 bpf 27861fc720be 443c11c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/27 15:30 bpf 27861fc720be e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/27 13:41 bpf 27861fc720be e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/25 21:44 bpf dd9de524183a bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/25 07:27 bpf dd9de524183a bf27483f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/25 04:26 bpf dd9de524183a bf27483f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/25 00:40 bpf dd9de524183a bf27483f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/24 18:51 bpf dd9de524183a bf27483f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/24 16:24 bpf dd9de524183a bf27483f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/24 13:45 bpf dd9de524183a bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/24 13:17 bpf dd9de524183a bf27483f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/08/24 11:18 bpf dd9de524183a bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
* Struck through repros no longer work on HEAD.