public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Update NEWS.
Date: Thu,  3 Feb 2022 05:15:17 +0000 (GMT)	[thread overview]
Message-ID: <20220203051517.E21253858C39@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=32ffd427413ab08566bbc051441fa7cfc082309b

commit 32ffd427413ab08566bbc051441fa7cfc082309b
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Wed Feb 2 23:46:19 2022 -0500

    Update NEWS.
    
    Moved LD_AUDIT notes into requirements section since the LAV_CURRENT
    bump is a requirements change that impacts loading old audit modules
    or new audit modules on older loaders.

Diff:
---
 NEWS | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/NEWS b/NEWS
index 119879e3dd..c489944c53 100644
--- a/NEWS
+++ b/NEWS
@@ -167,17 +167,18 @@ Deprecated and removed features, and other changes affecting compatibility:
   removal of the LD_TRACE_PRELINKING, and LD_USE_LOAD_BIAS, environment
   variables and their functionality in the dynamic loader.
 
+Changes to build and runtime requirements:
+
 * The audit module interface version LAV_CURRENT is increased to enable
   proper bind-now support.  The loader now advertises via the la_symbind
-  flags that PLT trace is not possible.
+  flags that PLT trace is not possible.  New audit modules require the
+  new dynamic loader supporing the latest LAV_CURRENT version. Old audit
+  modules are still loaded for all targets except aarch64.
 
 * The audit interface on aarch64 is extended to support both the indirect
   result location register (x8) and NEON Q register.  Old audit modules are
-  rejected by the loader.
-
-Changes to build and runtime requirements:
-
-  [Add changes to build and runtime requirements here]
+  rejected by the loader.  Audit modules must be rebuilt to use the newer
+  structure sizes and the latest module interface version for LAV_CURRENT.
 
 Security related changes:


             reply	other threads:[~2022-02-03  5:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  5:15 Carlos O'Donell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-01 20:49 Carlos O'Donell

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=20220203051517.E21253858C39@sourceware.org \
    --to=carlos@sourceware.org \
    --cc=glibc-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).