From: Aurelien Jarno <aurelien@aurel32.net>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-stable@sourceware.org
Subject: Re: Help backporting CVE-2022-23218 / bug 28768 to 2.33 and older
Date: Tue, 18 Jan 2022 18:57:54 +0100 [thread overview]
Message-ID: <Yeb/ohVhAk5LaInV@aurel32.net> (raw)
In-Reply-To: <87wnixlcvn.fsf@oldenburg.str.redhat.com>
On 2022-01-18 08:30, Florian Weimer wrote:
> * Aurelien Jarno:
>
> > Hi all,
> >
> > I am trying to backport commit f545ad4928fa to glibc 2.33 and older
> > releases. I noticed it contains a test which does not compile in such
> > branches due to the use of compat_symbol_reference.
> >
> > I see to options to fix that in the backport:
> > - backport commit 36f6e408845c8 ("<shlib-compat.h>: Support
> > compat_symbol_reference for _ISOMAC")
> > - move the test to tests-internal for older releases, just like it was
> > the case for some tests before the above commit.
> >
> > Which one of the two options is the best? Any other ideas?
>
> Backporting commit 36f6e408845c8 seems reasonable to me. Thanks.
Thanks for the help, I'll do that.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2022-01-18 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 6:57 Aurelien Jarno
2022-01-18 7:30 ` Florian Weimer
2022-01-18 17:57 ` Aurelien Jarno [this message]
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=Yeb/ohVhAk5LaInV@aurel32.net \
--to=aurelien@aurel32.net \
--cc=fweimer@redhat.com \
--cc=libc-stable@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).