bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "syeda-mahnur.asif" <syeda-mahnur.asif@mpi-sp.org>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net
Subject: Re: Sanitizer flags an eBPF bug
Date: Thu, 27 Nov 2025 14:59:14 +0100	[thread overview]
Message-ID: <da6b0f1c28c53e9e39ce3e949b0885c2@mpi-sp.org> (raw)
In-Reply-To: <cd5e012f7d365821707c9788bf382e3b@mpi-sp.org>

Hi,

Just wondering if there is any update on this?

Best regards,
Mahnur

On 2025-11-03 15:02, syeda-mahnur.asif wrote:
> Hi,
> 
> I've been playing around with eBPF and have sanitizers enabled, a "BUG: 
> Invalid wait context" is thrown in some specific instances:
> 1. The eBPF program is of Tracing type
> 2. Ringbuf helper functions are used.
> 3. The program is attached to perf_event related symbols in the kernel.
> 
> I'm attaching a folder with two instances of such programs and the info 
> dumped by the sanitizer. The attached files for each instance include:
> 1. bpf_prog(x).c
> 2. bpf_prog(x).o - object file that is compiled with "clang-16 -O2 -g 
> -target bpf -c bpf_progx.c -o bpf_progx.o" and loaded by libbpf (v1.6)
> 3. trig(x).c - File in C that is compiled as a binary and when executed 
> causes the bpf program to run
> 4. dump(x).txt - Sanitizer dump
> 5. vmlinux.h - Specific vmlinux file used in compiling the ebpf program 
> object files
> 
> Happy to provide any other additional info that might be relevant.
> 
> Best regards,
> Mahnur

  reply	other threads:[~2025-11-27 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 14:02 Sanitizer flags an eBPF bug syeda-mahnur.asif
2025-11-27 13:59 ` syeda-mahnur.asif [this message]
2025-12-09 16:15   ` syeda-mahnur.asif

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=da6b0f1c28c53e9e39ce3e949b0885c2@mpi-sp.org \
    --to=syeda-mahnur.asif@mpi-sp.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).