public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: John Mellor-Crummey <johnmc@rice.edu>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, Ben Woodard <woodard@redhat.com>,
	Jonathon Anderson <janderson@rice.edu>,
	Xiaozhu Meng <xm13@rice.edu>,
	"Mark W. Krentel" <krentel@rice.edu>,
	Matt Legendre <legendre1@llnl.gov>
Subject: Re: [PATCH 0/5] Some rtld-audit fixes
Date: Wed, 7 Jul 2021 20:09:47 -0400	[thread overview]
Message-ID: <098631BA-5017-492F-BC33-0A3D59578E7C@rice.edu> (raw)
In-Reply-To: <269adf45-f99a-6629-75ae-8a43bf906456@linaro.org>

actually, i am out july 17-30. schedule it the following week. the delay will not be a peoblem with the dept. 

(sent from my phone)

> On Jul 7, 2021, at 3:09 PM, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
> 
> 
> 
>> On 07/07/2021 16:02, John Mellor-Crummey wrote:
>> Adhemerval,
>> 
>> We are delighted to see your patches for the most troublesome problems (our Tier 1 issues) in glibc 2.34!! We look forward to installing a version of glibc with these patches soon and testing them.
>> 
>> In your email below, you mention that the ARM bugs are not fixed with this patch set and that they will be handled in a different patch set. Are you expecting that patch set to make it into 2.34 or not?
> 
> Hi John,
> 
> It is unlikely that they will make into 2.34 because we in the slush freeze
> that precedes the release and I haven't posted them previously. And they
> most likely required a ldaudit version bump.  I am aiming for next 2.35
> release. 
> 


  parent reply	other threads:[~2021-07-08  0:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 18:26 Adhemerval Zanella
2021-07-07 18:26 ` [PATCH 1/5] elf: Fix audit regression Adhemerval Zanella
2021-07-07 19:02   ` Florian Weimer
2021-07-07 19:07     ` Adhemerval Zanella
2021-07-07 19:51   ` Andreas Schwab
2021-07-07 19:57     ` Adhemerval Zanella
2021-07-07 20:02     ` Florian Weimer
2021-07-07 20:07       ` Florian Weimer
2021-07-08 12:13         ` Adhemerval Zanella
2021-07-07 18:26 ` [PATCH 2/5] elf: Avoid unnecessary slowdown from profiling with audit (BZ#15533) Adhemerval Zanella
2021-07-07 19:20   ` Florian Weimer
2021-07-07 20:05     ` Adhemerval Zanella
2021-07-07 20:15       ` Florian Weimer
2021-07-07 20:53         ` John Mellor-Crummey
2021-07-19 13:17         ` Adhemerval Zanella
2021-07-07 18:26 ` [PATCH 3/5] elf: Add audit tests for modules with TLSDESC Adhemerval Zanella
2021-07-07 18:26 ` [PATCH 4/5] elf: Do not fail for failed dlmopen on audit modules (BZ #28061) Adhemerval Zanella
2021-07-07 18:26 ` [PATCH 5/5] elf: Suppress audit calls when a (new) namespace is empty (BZ #28062) Adhemerval Zanella
2021-07-07 19:02 ` [PATCH 0/5] Some rtld-audit fixes John Mellor-Crummey
2021-07-07 19:09   ` Adhemerval Zanella
2021-07-07 19:22     ` John Mellor-Crummey
2021-07-08  6:25       ` Florian Weimer
2021-07-08  8:03         ` John Mellor-Crummey
2021-07-08  8:21           ` Florian Weimer
2021-07-08  0:09     ` John Mellor-Crummey [this message]
2021-07-08  0:11       ` John Mellor-Crummey

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=098631BA-5017-492F-BC33-0A3D59578E7C@rice.edu \
    --to=johnmc@rice.edu \
    --cc=adhemerval.zanella@linaro.org \
    --cc=janderson@rice.edu \
    --cc=krentel@rice.edu \
    --cc=legendre1@llnl.gov \
    --cc=libc-alpha@sourceware.org \
    --cc=woodard@redhat.com \
    --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).