[PATCH v2 0/3] Fix DTrace on modern kernels and in containers
Jacob Carlborg <[email protected]> Sat, 25 Jul 2026 20:04:06 +0200
| Newsgroups | dev.linux.lists.dtrace |
|---|---|
| Message-ID | <[email protected]> |
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. Changes since v1: - Patch 1: also treat BTF_KIND_TYPE_TAG as a transparent modifier in dt_btf_real_type_by_id() (per review feedback). Jacob Carlborg (3): libdtrace: resolve BTF type tags transparently 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 | 21 +++++++++++++- libdtrace/dt_prov_dtrace.c | 58 ++++++++++++++++++++++++++++++++++---- libdtrace/io.d.in | 17 +++++++++-- 3 files changed, 87 insertions(+), 9 deletions(-) -- 2.50.1 (Apple Git-155)