syzbot


possible deadlock in __bpf_ringbuf_reserve

Status: upstream: reported C repro on 2024/03/12 16:41
Subsystems: bpf
[Documentation on labels]
Reported-by: syzbot+850aaf14624dc0c6d366@syzkaller.appspotmail.com
First crash: 384d, last: 46m
Cause bisection: failed (error log, bisect log)
  
Discussions (10)
Title Replies (including bot) Last reply
[syzbot] Monthly bpf report (Mar 2025) 0 (1) 2025/03/23 22:24
[syzbot] Monthly bpf report (Feb 2025) 0 (1) 2025/02/20 19:03
[syzbot] Monthly bpf report (Jan 2025) 0 (1) 2025/01/20 08:14
[syzbot] Monthly bpf report (Dec 2024) 0 (1) 2024/12/19 21:40
[syzbot] Monthly bpf report (Oct 2024) 0 (1) 2024/10/15 21:53
[syzbot] Monthly bpf report (Sep 2024) 0 (1) 2024/09/14 12:53
[syzbot] Monthly bpf report (Aug 2024) 0 (1) 2024/08/14 12:43
[syzbot] Monthly bpf report (Jul 2024) 0 (1) 2024/07/15 11:52
[syzbot] Monthly bpf report (Jun 2024) 0 (1) 2024/06/12 22:41
[syzbot] [bpf?] possible deadlock in __bpf_ringbuf_reserve 6 (8) 2024/03/13 12:13
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in __bpf_ringbuf_reserve origin:upstream missing-backport C 67 7d21h 384d 0/3 upstream: reported C repro on 2024/03/08 23:13
Last patch testing requests (3)
Created Duration User Patch Repo Result
2024/03/24 09:45 21m retest repro bpf report log
2024/03/24 09:45 17m retest repro bpf-next report log
2024/03/13 10:46 24m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master OK log

Sample crash report:
============================================
WARNING: possible recursive locking detected
6.13.0-rc5-syzkaller-00163-gab75170520d4 #0 Not tainted
--------------------------------------------
syz-executor143/5962 is trying to acquire lock:
ffffc90006b050d8 (&rb->spinlock){..-.}-{2:2}, at: __bpf_ringbuf_reserve+0x36e/0x4b0 kernel/bpf/ringbuf.c:427

but task is already holding lock:
ffffc90006c0d0d8 (&rb->spinlock){..-.}-{2:2}, at: __bpf_ringbuf_reserve+0x36e/0x4b0 kernel/bpf/ringbuf.c:427

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 syz-executor143/5962:
 #0: ffffffff8e2d8368 (delayed_uprobe_lock){+.+.}-{4:4}, at: uprobe_clear_state+0x4b/0x1a0 kernel/events/uprobes.c:1771
 #1: ffffffff8e1bb900 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #1: ffffffff8e1bb900 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #1: ffffffff8e1bb900 (rcu_read_lock){....}-{1:3}, at: __bpf_trace_run kernel/trace/bpf_trace.c:2361 [inline]
 #1: ffffffff8e1bb900 (rcu_read_lock){....}-{1:3}, at: bpf_trace_run2+0x1c2/0x590 kernel/trace/bpf_trace.c:2403
 #2: ffffc90006c0d0d8 (&rb->spinlock){..-.}-{2:2}, at: __bpf_ringbuf_reserve+0x36e/0x4b0 kernel/bpf/ringbuf.c:427
 #3: ffffffff8e1bb900 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #3: ffffffff8e1bb900 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #3: ffffffff8e1bb900 (rcu_read_lock){....}-{1:3}, at: __bpf_trace_run kernel/trace/bpf_trace.c:2361 [inline]
 #3: ffffffff8e1bb900 (rcu_read_lock){....}-{1:3}, at: bpf_trace_run2+0x1c2/0x590 kernel/trace/bpf_trace.c:2403

stack backtrace:
CPU: 2 UID: 0 PID: 5962 Comm: syz-executor143 Not tainted 6.13.0-rc5-syzkaller-00163-gab75170520d4 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_deadlock_bug+0x2e3/0x410 kernel/locking/lockdep.c:3037
 check_deadlock kernel/locking/lockdep.c:3089 [inline]
 validate_chain kernel/locking/lockdep.c:3891 [inline]
 __lock_acquire+0x2117/0x3c40 kernel/locking/lockdep.c:5226
 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0x3a/0x60 kernel/locking/spinlock.c:162
 __bpf_ringbuf_reserve+0x36e/0x4b0 kernel/bpf/ringbuf.c:427
 ____bpf_ringbuf_reserve kernel/bpf/ringbuf.c:478 [inline]
 bpf_ringbuf_reserve+0x57/0x90 kernel/bpf/ringbuf.c:470
 bpf_prog_385141c453c15099+0x36/0x5d
 bpf_dispatcher_nop_func include/linux/bpf.h:1290 [inline]
 __bpf_prog_run include/linux/filter.h:701 [inline]
 bpf_prog_run include/linux/filter.h:708 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:2362 [inline]
 bpf_trace_run2+0x231/0x590 kernel/trace/bpf_trace.c:2403
 __bpf_trace_contention_begin+0xca/0x110 include/trace/events/lock.h:95
 __traceiter_contention_begin+0x5a/0xa0 include/trace/events/lock.h:95
 __preempt_count_dec_and_test arch/x86/include/asm/preempt.h:94 [inline]
 class_preempt_notrace_destructor include/linux/preempt.h:481 [inline]
 trace_contention_begin.constprop.0+0xf3/0x170 include/trace/events/lock.h:95
 __pv_queued_spin_lock_slowpath+0x10b/0xc90 kernel/locking/qspinlock.c:402
 pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:584 [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+0x210/0x2c0 kernel/locking/spinlock_debug.c:116
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:111 [inline]
 _raw_spin_lock_irqsave+0x42/0x60 kernel/locking/spinlock.c:162
 __bpf_ringbuf_reserve+0x36e/0x4b0 kernel/bpf/ringbuf.c:427
 ____bpf_ringbuf_reserve kernel/bpf/ringbuf.c:478 [inline]
 bpf_ringbuf_reserve+0x57/0x90 kernel/bpf/ringbuf.c:470
 bpf_prog_385141c453c15099+0x36/0x5d
 bpf_dispatcher_nop_func include/linux/bpf.h:1290 [inline]
 __bpf_prog_run include/linux/filter.h:701 [inline]
 bpf_prog_run include/linux/filter.h:708 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:2362 [inline]
 bpf_trace_run2+0x231/0x590 kernel/trace/bpf_trace.c:2403
 __bpf_trace_contention_begin+0xca/0x110 include/trace/events/lock.h:95
 __traceiter_contention_begin+0x5a/0xa0 include/trace/events/lock.h:95
 trace_contention_begin+0xd2/0x140 include/trace/events/lock.h:95
 __mutex_lock_common kernel/locking/mutex.c:587 [inline]
 __mutex_lock+0x1a8/0xa60 kernel/locking/mutex.c:735
 uprobe_clear_state+0x4b/0x1a0 kernel/events/uprobes.c:1771
 __mmput+0x79/0x4c0 kernel/fork.c:1344
 mmput+0x62/0x70 kernel/fork.c:1370
 exit_mm kernel/exit.c:570 [inline]
 do_exit+0x9ba/0x2d70 kernel/exit.c:925
 do_group_exit+0xd3/0x2a0 kernel/exit.c:1087
 __do_sys_exit_group kernel/exit.c:1098 [inline]
 __se_sys_exit_group kernel/exit.c:1096 [inline]
 __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1096
 x64_sys_call+0x151f/0x1720 arch/x86/include/generated/asm/syscalls_64.h:232
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff23ae2d0b9
Code: Unable to access opcode bytes at 0x7ff23ae2d08f.
RSP: 002b:00007ffdebef64b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff23ae2d0b9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007ff23aea82b0 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ff23aea82b0
R13: 0000000000000000 R14: 00007ff23aea8d20 R15: 00007ff23adfe240
 </TASK>

Crashes (2327):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/01/04 22:34 upstream ab75170520d4 f3558dbf .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __bpf_ringbuf_reserve
2025/01/19 11:58 net bc50835e83f6 f2cb035c .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/01/06 15:02 net 8ce4f287524c f3558dbf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/12/14 06:32 bpf e4c80f69758e 7cbfbb3a .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/10/06 09:44 bpf bcd28cfd04eb d7906eff .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/09/11 14:06 bpf b831f83e40a2 9326a104 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/05/31 02:02 net 068648aab72c 34889ee3 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/05/10 17:57 bpf 3e9bc0472b91 f7c35481 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/03/08 17:14 bpf df4793505abd cf82cde1 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/10/26 21:38 bpf-next 87cb58aebdf7 65e8686b .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/10/24 03:43 bpf-next 1f7c33630724 15fa2979 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/09/12 08:07 bpf-next c229c17a76e9 d94c83d8 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/09/08 09:34 bpf-next 8a3f14bb1e94 9750182a .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/03/08 19:47 bpf-next a27e89673abf cf82cde1 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/20 17:23 upstream a7f2e10ecd8f 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in __bpf_ringbuf_reserve
2025/03/18 04:32 upstream fc444ada1310 ce3352cd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in __bpf_ringbuf_reserve
2025/03/11 00:17 upstream 4d872d51bc9d 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __bpf_ringbuf_reserve
2025/03/10 22:25 upstream 80e54e84911a 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in __bpf_ringbuf_reserve
2025/03/14 12:19 upstream e3a854b577cb e2826670 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __bpf_ringbuf_reserve
2025/03/27 15:25 upstream 1a9239bb4253 928390c4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __bpf_ringbuf_reserve
2025/03/27 02:14 upstream f6e0150b2003 20510e88 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __bpf_ringbuf_reserve
2025/03/26 13:16 upstream 1e26c5e28ca5 19e40f48 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __bpf_ringbuf_reserve
2025/03/26 10:09 upstream 1e26c5e28ca5 89d30d73 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __bpf_ringbuf_reserve
2025/03/22 19:13 upstream 88d324e69ea9 c6512ef7 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __bpf_ringbuf_reserve
2025/03/26 04:52 bpf 6ccf6adb05d0 89d30d73 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/25 17:22 bpf 6ccf6adb05d0 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/25 04:06 bpf 6ccf6adb05d0 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/24 23:59 bpf 6ccf6adb05d0 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/22 20:16 bpf 6ccf6adb05d0 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/22 10:17 bpf 6ccf6adb05d0 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/22 08:04 bpf 6ccf6adb05d0 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/21 17:15 bpf 6ccf6adb05d0 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/19 05:48 bpf 6ccf6adb05d0 22a6c2b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/18 19:55 bpf 6ccf6adb05d0 22a6c2b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/09 08:10 net 505ead7ab77f 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/28 05:14 bpf-next 9aa8fe29f624 6c09fb82 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/28 03:39 bpf-next 9aa8fe29f624 6c09fb82 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/28 01:08 bpf-next 9aa8fe29f624 6c09fb82 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/27 19:40 bpf-next 9aa8fe29f624 6c09fb82 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/27 18:42 bpf-next 9aa8fe29f624 6c09fb82 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/27 17:24 bpf-next 9aa8fe29f624 20510e88 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/27 13:36 bpf-next 9aa8fe29f624 20510e88 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/27 11:36 net-next 023b1e9d265c 20510e88 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/27 09:37 bpf-next 9aa8fe29f624 20510e88 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/27 08:03 net-next 023b1e9d265c 20510e88 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/26 20:48 net-next a19f40d919ca 89d30d73 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/26 19:14 bpf-next 9aa8fe29f624 89d30d73 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/26 08:03 bpf-next 9aa8fe29f624 89d30d73 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/25 19:32 bpf-next 9aa8fe29f624 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/25 13:13 bpf-next 9aa8fe29f624 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/25 10:29 bpf-next 9aa8fe29f624 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/25 08:21 bpf-next 9aa8fe29f624 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/25 06:16 bpf-next 9aa8fe29f624 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/24 22:02 net-next 6bb0dcb3d321 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/24 04:47 bpf-next 9aa8fe29f624 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/23 21:50 net-next bfc17c165835 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/23 17:11 bpf-next 9aa8fe29f624 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/23 12:06 bpf-next 9aa8fe29f624 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/22 22:39 net-next bfc17c165835 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/21 23:23 bpf-next 307ef667e945 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/21 15:04 bpf-next 51d65049cd7e 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/20 20:31 bpf-next 79db658ad1cb 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/20 08:54 bpf-next a2598045ead9 3b7445cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/19 19:22 bpf-next ae0a457f5d33 8d0a2921 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/19 14:29 bpf-next ae0a457f5d33 8d0a2921 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/19 11:12 bpf-next ae0a457f5d33 8d0a2921 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/19 09:50 bpf-next ae0a457f5d33 8d0a2921 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2025/03/19 06:51 bpf-next ae0a457f5d33 22a6c2b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-bpf-next-kasan-gce possible deadlock in __bpf_ringbuf_reserve
2024/08/17 13:10 linux-next 367b5c3d53e5 dbc93b08 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __bpf_ringbuf_reserve
* Struck through repros no longer work on HEAD.