public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: John Mellor-Crummey <jmellorcrummey@icloud.com>
To: John Mellor-Crummey via Libc-alpha <libc-alpha@sourceware.org>
Cc: John Mellor-Crummey <jmellorcrummey@icloud.com>,
	Carlos O'Donell <carlos@redhat.com>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Michael Hudson-Doyle <michael.hudson@canonical.com>,
	Andreas Schwab <schwab@suse.de>,
	"Eachempati, Deepak" <deepak.eachempati@hpe.com>
Subject: Re: Backporting LD_AUDIT fixes to the glibc 2.34 release branch?
Date: Thu, 31 Mar 2022 14:58:22 -0500	[thread overview]
Message-ID: <E507FDBD-2929-4941-A7D8-2B2AE4BD4909@icloud.com> (raw)
In-Reply-To: <mailman.20300.1648586803.2100866.libc-alpha@sourceware.org>

We appreciate the plan to backport LD_AUDIT fixes to earlier glibc versions.

We are more than happy to rebuild all of our auditors to pickup the new LAV_CURRENT to get these fixes.

Besides a backport in RHEL, we would like to see the backport in a SUSE version delivered on Cray platforms
--
John Mellor-Crummey		Professor
Dept of Computer Science	Rice University
email: johnmc@rice.edu		phone: 713-348-5179

       reply	other threads:[~2022-03-31 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.20300.1648586803.2100866.libc-alpha@sourceware.org>
2022-03-31 19:58 ` John Mellor-Crummey [this message]
2022-03-29 20:46 Carlos O'Donell
2022-03-29 21:05 ` Carlos O'Donell
2022-03-29 22:36 ` Michael Hudson-Doyle
2022-03-30  9:19 ` Andreas Schwab
2022-03-30 16:18 ` Aurelien Jarno

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=E507FDBD-2929-4941-A7D8-2B2AE4BD4909@icloud.com \
    --to=jmellorcrummey@icloud.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=carlos@redhat.com \
    --cc=deepak.eachempati@hpe.com \
    --cc=libc-alpha@sourceware.org \
    --cc=michael.hudson@canonical.com \
    --cc=schwab@suse.de \
    /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).