From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: John Mellor-Crummey <johnmc@rice.edu>,
libc-alpha@sourceware.org, "Mark W. Krentel" <krentel@rice.edu>,
jma14 <jma14@rice.edu>, Xiaozhu Meng <xm13@rice.edu>
Subject: Re: Fwd: [PATCH v5 00/22] Some rtld-audit fixes
Date: Tue, 23 Nov 2021 13:25:43 -0300 [thread overview]
Message-ID: <b5475451-e1f8-401f-51ce-07caf7283dc1@linaro.org> (raw)
In-Reply-To: <87tug3rmv7.fsf@oldenburg.str.redhat.com>
On 23/11/2021 11:02, Florian Weimer wrote:
> * Adhemerval Zanella:
>
>> In fact I think rather than using the argv[0], since it passing the
>> executable path is just a convention; I think it would be better to
>> use AT_EXECFN. On recent kernel it is always passed to userland and
>> kernel should be responsible to hide any filesystem information if it
>> is required.
>
> It's still a relative path to an unknown directory, I think. I expect
> (but have not checked) that it is the pathname argument to execveat,
> which may not be meaningful to the new process image.
Yes, but it better than _dl_argv[0] and/or an empty string. Without
proper kernel support we can not reliable get the path, in fact the
kernel might in fact hides it on purpose.
next prev parent reply other threads:[~2021-11-23 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 17:46 Fwd: [PATCH v5 00/22] Some rtld-audit fixes jma14 via Libc-alpha
2021-11-23 13:58 ` Adhemerval Zanella via Libc-alpha
2021-11-23 14:02 ` Florian Weimer via Libc-alpha
2021-11-23 16:25 ` Adhemerval Zanella via Libc-alpha [this message]
2021-11-23 16:50 ` Florian Weimer via Libc-alpha
2021-11-23 21:13 ` Jonathon Anderson via Libc-alpha
2021-11-25 17:56 ` Adhemerval Zanella via Libc-alpha
-- strict thread matches above, loose matches on Subject: below --
2021-11-22 17:46 jma14 via Libc-alpha
[not found] <EA69A62D-7C01-4536-B551-2609226053F2@rice.edu>
2021-11-17 18:08 ` John Mellor-Crummey via Libc-alpha
2021-11-17 20:42 ` Florian Weimer via Libc-alpha
2021-11-18 21:55 ` Jonathon Anderson via Libc-alpha
2021-11-19 19:18 ` Florian Weimer via Libc-alpha
2021-11-19 19:56 ` Adhemerval Zanella via Libc-alpha
2021-11-19 20:31 ` Florian Weimer via Libc-alpha
2021-11-23 16:36 ` Adhemerval Zanella via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5475451-e1f8-401f-51ce-07caf7283dc1@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=jma14@rice.edu \
--cc=johnmc@rice.edu \
--cc=krentel@rice.edu \
--cc=xm13@rice.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).