* Help backporting CVE-2022-23218 / bug 28768 to 2.33 and older
@ 2022-01-18 6:57 Aurelien Jarno
2022-01-18 7:30 ` Florian Weimer
0 siblings, 1 reply; 3+ messages in thread
From: Aurelien Jarno @ 2022-01-18 6:57 UTC (permalink / raw)
To: libc-stable; +Cc: Florian Weimer
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?
Thanks,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Help backporting CVE-2022-23218 / bug 28768 to 2.33 and older
2022-01-18 6:57 Help backporting CVE-2022-23218 / bug 28768 to 2.33 and older Aurelien Jarno
@ 2022-01-18 7:30 ` Florian Weimer
2022-01-18 17:57 ` Aurelien Jarno
0 siblings, 1 reply; 3+ messages in thread
From: Florian Weimer @ 2022-01-18 7:30 UTC (permalink / raw)
To: Aurelien Jarno; +Cc: libc-stable
* 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.
Florian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Help backporting CVE-2022-23218 / bug 28768 to 2.33 and older
2022-01-18 7:30 ` Florian Weimer
@ 2022-01-18 17:57 ` Aurelien Jarno
0 siblings, 0 replies; 3+ messages in thread
From: Aurelien Jarno @ 2022-01-18 17:57 UTC (permalink / raw)
To: Florian Weimer; +Cc: libc-stable
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-01-18 17:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-18 6:57 Help backporting CVE-2022-23218 / bug 28768 to 2.33 and older Aurelien Jarno
2022-01-18 7:30 ` Florian Weimer
2022-01-18 17:57 ` Aurelien Jarno
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).