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@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH] pid: USDT probes cannot have "-" as function name
Date: Mon, 9 Feb 2026 14:37:08 -0500 [thread overview]
Message-ID: <aYo3ZO/boPXs4NBW@oracle.com> (raw)
In-Reply-To: <a1051394-2811-d0e7-ecc4-f421396b2bf4@oracle.com>
On Mon, Feb 09, 2026 at 02:22:11PM -0500, Eugene Loh wrote:
> Could we have a little more explanation here? Like, what is wrong with the
> current behavior (which is... to complain that the probe is not found?)?
> And should any test check the behavior?
It is an optimization. That is why I added it right above the test to see
if there is a pid in the provider name. That was also an optimization. In
both cases we bail if we can determine immediately that the presented probedesc
cannot be a USDT probe.
> On 2/9/26 13:35, Kris Van Hees via DTrace-devel wrote:
> > Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
> > ---
> > libdtrace/dt_pid.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/libdtrace/dt_pid.c b/libdtrace/dt_pid.c
> > index 517b9265..ef97c8d9 100644
> > --- a/libdtrace/dt_pid.c
> > +++ b/libdtrace/dt_pid.c
> > @@ -1568,6 +1568,10 @@ dt_pid_create_usdt_probes(dtrace_probedesc_t *pdp, dtrace_hdl_t *dtp)
> > char *globpat = NULL;
> > int err = 0, i, nmatches = 0;
> > + /* If the function name is "-", we're done. */
> > + if (pdp->fun[0] == '-' && pdp->fun[1] == '\0')
> > + return 0;
> > +
> > /* If it cannot end with a pid, we're done. */
> > if (pdp->prv[0] != '\0') {
> > char lastchar = pdp->prv[strlen(pdp->prv) - 1];
next prev parent reply other threads:[~2026-02-09 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 18:35 [PATCH] pid: USDT probes cannot have "-" as function name Kris Van Hees
2026-02-09 19:22 ` [DTrace-devel] " Eugene Loh
2026-02-09 19:37 ` Kris Van Hees [this message]
2026-02-09 19:38 ` Eugene Loh
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=aYo3ZO/boPXs4NBW@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