Re: [PATCH 0/3] Fix DTrace on modern kernels and in containers

[Kris Van Hees <kris.van.hees@oracle.com>]

Thanks for reporting these issues and sending patches.  It ceetainly highlights
an area where our testing is lacking, i.e. containers and related namespace
issues.  That will need some attention as well.


On Mon, Jul 20, 2026 at 03:30:57PM +0200, Jacob Carlborg wrote:
> 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
> 
> 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)
> 
> 
>