From: Alejandro Colomar <alx@kernel.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: linux-man@vger.kernel.org, alx.manpages@gmail.com
Subject: Re: [PATCH 2/5] ld.so.8: Clarify LD_PROFILE in secure-execution mode
Date: Wed, 18 Oct 2023 21:19:19 +0200 [thread overview]
Message-ID: <ZTAvvolND_9zrcRL@debian> (raw)
In-Reply-To: <20231018172104.1196993-3-adhemerval.zanella@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]
Hi Adhemerval,
On Wed, Oct 18, 2023 at 02:21:01PM -0300, Adhemerval Zanella wrote:
> Different than specified, glibc 2.2.5 does not ignore LD_PROFILE in
The text being removed talks about glibc _before_ 2.2.5, that is,
every version until 2.2.4. That doesn't match the commit message.
Please check.
Thanks,
Alex
> secure-execution mode. Instead, it uses the default LD_PROFILE_OUTPUT
> (/var/profile) folder.
>
> Signed-off-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> ---
> man8/ld.so.8 | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/man8/ld.so.8 b/man8/ld.so.8
> index 5b5c22825..74286d583 100644
> --- a/man8/ld.so.8
> +++ b/man8/ld.so.8
> @@ -664,7 +664,7 @@ Profiling output is appended to the file whose name is:
> .IP
> Since glibc 2.2.5,
> .B LD_PROFILE
> -is ignored in secure-execution mode.
> +uses a different default path in secure-execution mode.
> .TP
> .BR LD_PROFILE_OUTPUT " (since glibc 2.1)"
> Directory where
> @@ -672,16 +672,13 @@ Directory where
> output should be written.
> If this variable is not defined, or is defined as an empty string,
> then the default is
> -.IR /var/tmp .
> +.IR /var/tmp
> +or
> +.IR /var/profile
> +in secure-execution mode.
> .IP
> .B LD_PROFILE_OUTPUT
> -is ignored in secure-execution mode; instead
> -.I /var/profile
> -is always used.
> -(This detail is relevant only before glibc 2.2.5,
> -since in later glibc versions,
> -.B LD_PROFILE
> -is also ignored in secure-execution mode.)
> +is ignored in secure-execution mode.
> .TP
> .BR LD_SHOW_AUXV " (since glibc 2.1)"
> If this environment variable is defined (with any value),
> --
> 2.34.1
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-18 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 17:20 [PATCH 0/5] Some ld.so updates Adhemerval Zanella
2023-10-18 17:21 ` [PATCH 1/5] ld.so.8: Update environment variables from recent glibc versions Adhemerval Zanella
2023-10-18 19:06 ` Alejandro Colomar
2023-10-18 20:36 ` Adhemerval Zanella Netto
2023-10-18 17:21 ` [PATCH 2/5] ld.so.8: Clarify LD_PROFILE in secure-execution mode Adhemerval Zanella
2023-10-18 19:19 ` Alejandro Colomar [this message]
2023-10-18 20:47 ` Adhemerval Zanella Netto
2023-10-19 12:54 ` Alejandro Colomar
2023-10-18 17:21 ` [PATCH 3/5] ld.so.8: Add add filtered out environment variable " Adhemerval Zanella
2023-10-18 19:25 ` Alejandro Colomar
2023-10-18 17:21 ` [PATCH 4/5] ld.so.8: Describe glibc Hardware capabilities Adhemerval Zanella
2023-10-18 19:50 ` Alejandro Colomar
2023-10-18 17:21 ` [PATCH 5/5] ld.so.8: Describe the --list-diagnostics loader option Adhemerval Zanella
2023-10-18 19:56 ` Alejandro Colomar
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=ZTAvvolND_9zrcRL@debian \
--to=alx@kernel.org \
--cc=adhemerval.zanella@linaro.org \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
/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