From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace-devel@oss.oracle.com, dtrace@lists.linux.dev
Subject: Re: [DTrace-devel] [PATCH 1/3] pid: ensure pid offset probes perform lookup with adjusted address
Date: Tue, 10 Feb 2026 15:18:45 +0000 [thread overview]
Message-ID: <87o6lwr5ii.fsf@esperi.org.uk> (raw)
In-Reply-To: <DS0PR10MB7522F3DF908967F8E1681F5BC265A@DS0PR10MB7522.namprd10.prod.outlook.com> (Kris Van Hees via DTrace-devel's message of "Mon, 09 Feb 2026 15:43:47 -0500")
On 9 Feb 2026, Kris Van Hees via DTrace-devel stated:
> For PIE executables and libraries, pid offset probes need to have the
> address adjusted based on the actual segment load address.
>
> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Looks good (in particular it's good that we're actually recording that
this is PIE rather than relying on a usually-right guess), modulo one
tiny nit:
> ---
> include/sys/sol_procfs.h | 3 ++-
> libdtrace/dt_pid.c | 3 +++
> libproc/Psymtab.c | 7 +++++--
> 3 files changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/include/sys/sol_procfs.h b/include/sys/sol_procfs.h
> index d195a108..950ab31a 100644
> --- a/include/sys/sol_procfs.h
> +++ b/include/sys/sol_procfs.h
> @@ -1,6 +1,6 @@
> /*
> * Oracle Linux DTrace.
> - * Copyright (c) 2006, 2022, Oracle and/or its affiliates. All rights reserved.
> + * Copyright (c) 2006, 2026, Oracle and/or its affiliates. All rights reserved.
> * Licensed under the Universal Permissive License v 1.0 as shown at
> * http://oss.oracle.com/licenses/upl.
> */
> @@ -50,6 +50,7 @@ typedef struct prmap {
>
>
> /* Protection and attribute flags */
> +#define MA_PIC 0x08 /* position independent code */
> #define MA_READ 0x04 /* readable by the traced process */
Tab/space?
--
NULL && (void)
prev parent reply other threads:[~2026-02-10 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 20:43 [PATCH 1/3] pid: ensure pid offset probes perform lookup with adjusted address Kris Van Hees
2026-02-10 15:18 ` Nick Alcock [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=87o6lwr5ii.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@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