Linux DTrace development list
 help / color / mirror / Atom feed
From: Jacob Carlborg <doob@me.com>
To: dtrace@lists.linux.dev
Cc: Jacob Carlborg <doob@me.com>
Subject: [PATCH 0/3] Fix DTrace on modern kernels and in containers
Date: Mon, 20 Jul 2026 15:30:57 +0200	[thread overview]
Message-ID: <20260720133100.77573-1-doob@me.com> (raw)

Hi, I've created three patches for the issues I've encountered when trying to
get DTrace to work in my environments. One environment is on my local computer
running macOS ARM64 using Docker through OrbStack. The other is our Kubernetes
cluster in the cloud. The first two issues are differences in the Linux kernel
compared to what DTrace expects. The third issue is container related.

The OrbStack environment is running version 7.0.11 of the Linux kernel. The
Kubernetes cluster is running 6.12.85.

I'll be honest, the analysis of the issues and the patches are all done by an
AI. I've verified everything manually myself.

Jacob Carlborg (3):
  libdtrace: resolve BTF type tags when importing BTF into CTF
  libdtrace: derive io provider dev_name from the device model
  libdtrace: match BEGIN/END PID in the tracer's own PID namespace

 libdtrace/dt_btf.c         | 20 ++++++++++++-
 libdtrace/dt_prov_dtrace.c | 58 ++++++++++++++++++++++++++++++++++----
 libdtrace/io.d.in          | 17 +++++++++--
 3 files changed, 86 insertions(+), 9 deletions(-)

--
2.50.1 (Apple Git-155)


             reply	other threads:[~2026-07-20 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 13:30 Jacob Carlborg [this message]
2026-07-20 13:30 ` [PATCH 1/3] libdtrace: resolve BTF type tags when importing BTF into CTF Jacob Carlborg
2026-07-20 13:30 ` [PATCH 2/3] libdtrace: derive io provider dev_name from the device model Jacob Carlborg
2026-07-20 13:31 ` [PATCH 3/3] libdtrace: match BEGIN/END PID in the tracer's own PID namespace Jacob Carlborg
2026-07-20 16:33 ` [PATCH 0/3] Fix DTrace on modern kernels and in containers Kris Van Hees
2026-07-21  6:27   ` Jacob Carlborg

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=20260720133100.77573-1-doob@me.com \
    --to=doob@me.com \
    --cc=dtrace@lists.linux.dev \
    /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