From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
DTrace development list <dtrace-devel@oss.oracle.com>,
DTrace dev list <dtrace@lists.linux.dev>
Subject: Re: Test that PASSes but should not
Date: Thu, 24 Jul 2025 17:00:27 -0400 [thread overview]
Message-ID: <aIKe6xg/Y0ElXnTO@oracle.com> (raw)
In-Reply-To: <d682398d-d1fe-a788-d8d4-3b9fbc4ea260@oracle.com>
On Thu, Jul 24, 2025 at 04:54:19PM -0400, Eugene Loh wrote:
> On 7/24/25 14:57, Kris Van Hees wrote:
>
> > On Thu, Jul 24, 2025 at 02:34:00PM -0400, Kris Van Hees wrote:
> > > On Thu, Jul 24, 2025 at 02:21:36PM -0400, Eugene Loh wrote:
> > > > And yet it has a .r file?
> > > Yes, the problem is less with the test and more with something going wrong with
> > > BTF handling causing the probe to not have a BTF ID and yet it is trying to
> > > load a program for it. Attachment should not even be tried in that case.
> > >
> > > Working out what is wrong and fixing.
> > Patch posted. Was an issue with the BTF ID lookup code handling modules
> > whose BTF data didn't get initialized yet.
>
> But how could it dump all that stuff and pass matching against a .r file?
No idea - my priority right now was fixing the issue that caused the BPF
verifier error report. We can look at why it was deemed to PASS even with
that BPF verifer complaint - that is secondary.
prev parent reply other threads:[~2025-07-24 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 17:25 Test that PASSes but should not Kris Van Hees
2025-07-24 18:21 ` Eugene Loh
2025-07-24 18:34 ` Kris Van Hees
2025-07-24 18:57 ` Kris Van Hees
2025-07-24 20:54 ` Eugene Loh
2025-07-24 21:00 ` Kris Van Hees [this message]
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=aIKe6xg/Y0ElXnTO@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.com \
/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