syzbot


possible deadlock in __bpf_ringbuf_reserve

Status: upstream: reported C repro on 2025/07/04 03:51
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+33bfc46927a4ecf45b6d@syzkaller.appspotmail.com
First crash: 195d, last: 5d14h
Fix bisection: the issue occurs on the latest tested release (bisect log)
Crash: possible deadlock in __bpf_ringbuf_reserve (log)
Repro: C syz .config
  
Bug presence (2)
Date Name Commit Repro Result
2025/07/07 linux-6.6.y (ToT) a5df3a702b2c C [report] possible deadlock in __bpf_ringbuf_reserve
2025/07/07 upstream (ToT) d7b8f8e20813 C Didn't crash
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 90 36d 677d 0/3 upstream: reported C repro on 2024/03/08 23:13
upstream possible deadlock in __bpf_ringbuf_reserve (2) bpf 4 C done error 22 127d 142d 0/29 auto-obsoleted due to no activity on 2025/11/18 12:07
linux-5.15 possible deadlock in __bpf_ringbuf_reserve 4 1 132d 132d 0/3 auto-obsoleted due to no activity on 2025/12/13 22:27
upstream possible deadlock in __bpf_ringbuf_reserve bpf 4 C error 2490 268d 673d 28/29 fixed on 2025/06/10 16:19
Fix bisection attempts (3)
Created Duration User Patch Repo Result
2025/12/07 19:18 1h50m fix candidate upstream OK (0) job log
2025/11/04 16:31 1h38m bisect fix linux-6.6.y OK (0) job log log
2025/08/29 07:46 1h28m bisect fix linux-6.6.y OK (0) job log log

Sample crash report:
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
kworker/u4:13/3507 is trying to acquire lock:
ffffc9000dd790d8 (&rb->spinlock){-.-.}-{2:2}, at: __bpf_ringbuf_reserve+0x1c8/0x5a0 kernel/bpf/ringbuf.c:425

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

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

6 locks held by kworker/u4:13/3507:
 #0: ffff888017871538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #0: ffff888017871538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #1: ffffc9000cd87d00 ((work_completion)(&rdev->wiphy_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc9000cd87d00 ((work_completion)(&rdev->wiphy_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffff88802d020768 (&rdev->wiphy.mtx){+.+.}-{3:3}, at: wiphy_lock include/net/cfg80211.h:5777 [inline]
 #2: ffff88802d020768 (&rdev->wiphy.mtx){+.+.}-{3:3}, at: cfg80211_wiphy_work+0x35/0x260 net/wireless/core.c:424
 #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_run3+0xf4/0x400 kernel/trace/bpf_trace.c:2362
 #4: ffffc9000de130d8 (&rb->spinlock){-.-.}-{2:2}, at: __bpf_ringbuf_reserve+0x1c8/0x5a0 kernel/bpf/ringbuf.c:425
 #5: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #5: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #5: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: trace_call_bpf+0xc3/0x690 kernel/trace/bpf_trace.c:142

stack backtrace:
CPU: 0 PID: 3507 Comm: kworker/u4:13 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: events_unbound cfg80211_wiphy_work
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
 __bpf_ringbuf_reserve+0x1c8/0x5a0 kernel/bpf/ringbuf.c:425
 ____bpf_ringbuf_reserve kernel/bpf/ringbuf.c:476 [inline]
 bpf_ringbuf_reserve+0x5c/0x70 kernel/bpf/ringbuf.c:468
 bpf_prog_df2ea1bb7efca089+0x35/0x4f
 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_prog_run_array include/linux/bpf.h:1994 [inline]
 trace_call_bpf+0x321/0x690 kernel/trace/bpf_trace.c:143
 perf_trace_run_bpf_submit+0x7a/0x1c0 kernel/events/core.c:10263
 perf_trace_contention_begin+0x254/0x2f0 include/trace/events/lock.h:95
 trace_contention_begin+0xe9/0x110 include/trace/events/lock.h:95
 __pv_queued_spin_lock_slowpath+0xe0/0x9d0 kernel/locking/qspinlock.c:405
 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
 __bpf_ringbuf_reserve+0x1c8/0x5a0 kernel/bpf/ringbuf.c:425
 ____bpf_ringbuf_output kernel/bpf/ringbuf.c:551 [inline]
 bpf_ringbuf_output+0x69/0x1e0 kernel/bpf/ringbuf.c:541
 bpf_prog_918f90024333f9ff+0x42/0x46
 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_run3+0x1e7/0x400 kernel/trace/bpf_trace.c:2362
 __bpf_trace_kfree_skb+0x14a/0x1b0 include/trace/events/skb.h:24
 __traceiter_kfree_skb+0x77/0xc0 include/trace/events/skb.h:24
 trace_kfree_skb+0x174/0x1d0 include/trace/events/skb.h:24
 __kfree_skb_reason net/core/skbuff.c:1090 [inline]
 kfree_skb_reason+0xcf/0x170 net/core/skbuff.c:1106
 kfree_skb include/linux/skbuff.h:1232 [inline]
 ieee80211_iface_work+0x788/0xc70 net/mac80211/iface.c:1707
 cfg80211_wiphy_work+0x225/0x260 net/wireless/core.c:437
 process_one_work kernel/workqueue.c:2634 [inline]
 process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
 worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
 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 (35):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/01/06 04:46 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 __bpf_ringbuf_reserve
2025/09/25 07:28 linux-6.6.y af1544b5d072 0abd0691 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in __bpf_ringbuf_reserve
2025/09/12 16:52 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 __bpf_ringbuf_reserve
2025/09/10 06:56 linux-6.6.y fe9731e10004 fdeaa69b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in __bpf_ringbuf_reserve
2025/09/09 23:04 linux-6.6.y fe9731e10004 d291dd2d .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in __bpf_ringbuf_reserve
2025/09/09 17:24 linux-6.6.y 355bd0b51d2f d291dd2d .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan-perf possible deadlock in __bpf_ringbuf_reserve
2025/07/25 20:15 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 __bpf_ringbuf_reserve
2025/07/07 09:05 linux-6.6.y a5df3a702b2c 4f67c4ae .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2026/01/09 20:57 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 __bpf_ringbuf_reserve
2026/01/06 01:11 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 __bpf_ringbuf_reserve
2025/12/18 08: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 __bpf_ringbuf_reserve
2025/12/01 18:34 linux-6.6.y 4791134e4aeb d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/26 00:59 linux-6.6.y 1e89a1be4fe9 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/26 00:59 linux-6.6.y 1e89a1be4fe9 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/26 00:54 linux-6.6.y 1e89a1be4fe9 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/26 00:52 linux-6.6.y 1e89a1be4fe9 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/21 12:08 linux-6.6.y 0a805b6ea8cd 280ea308 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/21 12:08 linux-6.6.y 0a805b6ea8cd 280ea308 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/21 12:06 linux-6.6.y 0a805b6ea8cd 280ea308 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/20 15:43 linux-6.6.y 0a805b6ea8cd 2cc4c24a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/11/15 22:46 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 __bpf_ringbuf_reserve
2025/11/13 10:36 linux-6.6.y 0a805b6ea8cd 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/09/18 15:36 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/09/18 15:35 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/09/17 21: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 __bpf_ringbuf_reserve
2025/09/17 21:32 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/09/13 19:27 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/09/13 19:26 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/09/13 19: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 __bpf_ringbuf_reserve
2025/09/13 19:06 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 __bpf_ringbuf_reserve
2025/09/10 21:07 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 __bpf_ringbuf_reserve
2025/07/10 21:25 linux-6.6.y 59a2de10b81a 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/07/06 15:19 linux-6.6.y a5df3a702b2c 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/07/04 18:38 linux-6.6.y 3f5b4c104b7d d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
2025/07/04 03:51 linux-6.6.y 3f5b4c104b7d 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in __bpf_ringbuf_reserve
* Struck through repros no longer work on HEAD.