From: Kris Van Hees <kris.van.hees@oracle.com>
To: Nick Alcock <nix@esperi.org.uk>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 11/20] libdtrace: cache missing kernel CTF archives until paths change
Date: Fri, 6 Nov 2026 16:24:49 -0500 [thread overview]
Message-ID: <au5FobRpMWygAUHU@oracle.com> (raw)
In-Reply-To: <875wyat8qq.fsf@esperi.org.uk>
On Fri, Nov 06, 2026 at 01:00:45PM +0000, Nick Alcock wrote:
> On 30 Oct 2026, Kris Van Hees said:
>
> > ---
> > libdtrace/dt_impl.h | 1 +
> > libdtrace/dt_module.c | 16 +++++++++++--
> > libdtrace/dt_options.c | 3 +++
> > test/triggers/Build | 1 +
> > test/triggers/shared-ctf.c | 49 ++++++++++++++++++++++++++++++++++++++
> > 5 files changed, 68 insertions(+), 2 deletions(-)
>
> ... why on earth would they ever be missing? Surely fixing that instead
> is a good idea? (Or is this something to do with chroots and containers
> and the CTFA being in a filesystem path whose meaning will change in the
> middle of execution or something?)
This was prompted by tests for the ctfpath option.
prev parent reply other threads:[~2026-11-06 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:36 [PATCH 11/20] libdtrace: cache missing kernel CTF archives until paths change Kris Van Hees
2026-11-06 13:00 ` Nick Alcock
2026-11-06 21:24 ` 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=au5FobRpMWygAUHU@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=nix@esperi.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.