public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
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 14:34:00 -0400	[thread overview]
Message-ID: <aIJ8mKI0nSZviJnc@oracle.com> (raw)
In-Reply-To: <a7197497-1d4a-f68b-f62e-5819e94515f3@oracle.com>

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.

> On 7/24/25 13:25, Kris Van Hees wrote:
> > This is not a good thing:
> > 
> > test/unittest/ip/tst.ipv4localicmp.sh: Running timeout --signal=TERM 41 test/unittest/ip/tst.ipv4localicmp.sh /home/kvanhees/dtrace-bpf-user/build/dtrace
> > PASS.
> > -- @@stderr --
> > BPF: func#0 @0
> > BPF: func#1 @154
> > BPF: func#2 @1121
> > BPF: func#3 @1136
> > BPF: func#4 @1350
> > BPF: func#5 @1355
> > BPF: func#6 @1438
> > BPF: func#7 @1453
> > BPF: func#8 @1667
> > BPF: func#9 @1706
> > BPF: func#10 @1746
> > BPF: func#11 @1926
> > BPF: func#12 @1995
> > BPF: func#13 @2064
> > BPF: func#14 @2074
> > BPF: Tracing programs must provide btf_id
> > BPF: verification time 33 usec
> > BPF: stack depth 0+0+0+0+0+0+0+0+0+0+0+0+0+0+0
> > BPF: processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
> > dtrace: could not enable tracing: BPF program load for 'fbt:ipv6:ip6_finish_output:entry' failed: Invalid argument
> > 
> > That failure definitely should cause the test to fail.
> > 

  reply	other threads:[~2025-07-24 18:34 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 [this message]
2025-07-24 18:57     ` Kris Van Hees
2025-07-24 20:54       ` Eugene Loh
2025-07-24 21:00         ` Kris Van Hees

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=aIJ8mKI0nSZviJnc@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