public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/5] ld.so.8: Update environment variables from recent glibc versions
Date: Wed, 18 Oct 2023 21:06:22 +0200	[thread overview]
Message-ID: <ZTAsrnUGVgUll56p@debian> (raw)
In-Reply-To: <20231018172104.1196993-2-adhemerval.zanella@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 4586 bytes --]

Hi Adhemerval!

On Wed, Oct 18, 2023 at 02:21:00PM -0300, Adhemerval Zanella wrote:
> Recent glibc version removed support for LD_TRACE_PRELINKING,
> LD_ASSUME_KERNEL, and LD_USE_LOAD_BIAS.
> 
> Also adds a note for LD_HWCAP_MASk that since 2.26 the environment
> variable might be ignored if glibc does not support tunables.
> 
> Signed-off-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> ---

Patch applied.  Thanks!

I've also applied some small fixes for consistency, and to use "semantic
newlines".  See below.

Cheers,
Alex

P.S.:
I'm deprecating <alx.manpages@gmail.com>; please use <alx@kernel.org>.

---

diff --git a/man8/ld.so.8 b/man8/ld.so.8
index 5b5c22825..1999c24d6 100644
--- a/man8/ld.so.8
+++ b/man8/ld.so.8
@@ -310,7 +310,7 @@ .SS Secure-execution mode
 .SS Environment variables
 Among the more important environment variables are the following:
 .TP
-.BR LD_ASSUME_KERNEL " (from glibc 2.2.3 to 2.36)"
+.BR LD_ASSUME_KERNEL " (from glibc 2.2.3 to glibc 2.36)"
 Each shared object can inform the dynamic linker of the minimum kernel ABI
 version that it requires.
 (This requirement is encoded in an ELF note section that is viewable via
@@ -628,7 +628,9 @@ .SS Environment variables
 is ignored in secure-execution mode.
 .TP
 .BR LD_HWCAP_MASK " (from glibc 2.1 to glibc 2.38)"
-Mask for hardware capabilities.  Since glibc 2.26 the option might be ignored
+Mask for hardware capabilities.
+Since glibc 2.26,
+the option might be ignored
 if glibc does not support tunables.
 .TP
 .BR LD_ORIGIN_PATH " (since glibc 2.1)"
@@ -703,7 +705,7 @@ .SS Environment variables
 .\" (This is what seems to happen, from experimenting)
 then all prelinking activity is traced.
 .TP
-.BR LD_USE_LOAD_BIAS " (from glibc 2.3.3 to 2.35)"
+.BR LD_USE_LOAD_BIAS " (from glibc 2.3.3 to glibc 2.35)"
 .\" http://sources.redhat.com/ml/libc-hacker/2003-11/msg00127.html
 .\" Subject: [PATCH] Support LD_USE_LOAD_BIAS
 .\" Jakub Jelinek


$ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p'
   Use semantic newlines
       In the source of a manual page, new sentences should be started
       on  new  lines,  long  sentences  should be split into lines at
       clause breaks (commas, semicolons, colons, and so on), and long
       clauses should be split at phrase boundaries.  This convention,
       sometimes known as "semantic newlines", makes it easier to  see
       the  effect of patches, which often operate at the level of in‐
       dividual sentences, clauses, or phrases.

>  man8/ld.so.8 | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/man8/ld.so.8 b/man8/ld.so.8
> index 900f3a9b9..5b5c22825 100644
> --- a/man8/ld.so.8
> +++ b/man8/ld.so.8
> @@ -310,7 +310,7 @@ A nonzero value may have been set by a Linux Security Module.
>  .SS Environment variables
>  Among the more important environment variables are the following:
>  .TP
> -.BR LD_ASSUME_KERNEL " (since glibc 2.2.3)"
> +.BR LD_ASSUME_KERNEL " (from glibc 2.2.3 to 2.36)"
>  Each shared object can inform the dynamic linker of the minimum kernel ABI
>  version that it requires.
>  (This requirement is encoded in an ELF note section that is viewable via
> @@ -627,8 +627,9 @@ Since glibc 2.3.4,
>  .B LD_DYNAMIC_WEAK
>  is ignored in secure-execution mode.
>  .TP
> -.BR LD_HWCAP_MASK " (since glibc 2.1)"
> -Mask for hardware capabilities.
> +.BR LD_HWCAP_MASK " (from glibc 2.1 to glibc 2.38)"
> +Mask for hardware capabilities.  Since glibc 2.26 the option might be ignored
> +if glibc does not support tunables.
>  .TP
>  .BR LD_ORIGIN_PATH " (since glibc 2.1)"
>  Path where the binary is found.
> @@ -691,7 +692,7 @@ Since glibc 2.3.4,
>  .B LD_SHOW_AUXV
>  is ignored in secure-execution mode.
>  .TP
> -.BR LD_TRACE_PRELINKING " (since glibc 2.4)"
> +.BR LD_TRACE_PRELINKING " (from glibc 2.4 to glibc 2.35)"
>  If this environment variable is defined,
>  trace prelinking of the object whose name is assigned to
>  this environment variable.
> @@ -702,7 +703,7 @@ If the object name is not recognized,
>  .\" (This is what seems to happen, from experimenting)
>  then all prelinking activity is traced.
>  .TP
> -.BR LD_USE_LOAD_BIAS " (since glibc 2.3.3)"
> +.BR LD_USE_LOAD_BIAS " (from glibc 2.3.3 to 2.35)"
>  .\" http://sources.redhat.com/ml/libc-hacker/2003-11/msg00127.html
>  .\" Subject: [PATCH] Support LD_USE_LOAD_BIAS
>  .\" Jakub Jelinek
> -- 
> 2.34.1
> 

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-10-18 19:06 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 [this message]
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
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=ZTAsrnUGVgUll56p@debian \
    --to=alx@kernel.org \
    --cc=adhemerval.zanella@linaro.org \
    --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