[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202202231957.801F1780@keescook>
Date: Wed, 23 Feb 2022 19:58:58 -0800
From: Kees Cook <keescook@...omium.org>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc: Thorsten Leemhuis <regressions@...mhuis.info>,
Anthony Yznaga <anthony.yznaga@...cle.com>,
matoro_bugzilla_kernel@...oro.tk,
Andrew Morton <akpm@...ux-foundation.org>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
linux-ia64@...r.kernel.org,
Linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Alexander Viro <viro@...iv.linux.org.uk>
Subject: Re: regression: Bug 215601 - gcc segv at startup on ia64
On Mon, Feb 21, 2022 at 10:57:01PM +0100, John Paul Adrian Glaubitz wrote:
> Hi Kees!
>
> On 2/21/22 21:58, Kees Cook wrote:
> >> I have applied this patch on top of 038101e6b2cd5c55f888f85db42ea2ad3aecb4b6 and it doesn't
> >> fix the problem for me. Reverting 5f501d555653f8968011a1e65ebb121c8b43c144, however, fixes
> >> the problem.
> >>
> >> FWIW, this problem doesn't just affect GCC but systemd keeps segfaulting with this change as well.
> >
> > Very weird! Can you attached either of those binaries to bugzilla (or a URL I can fetch it from)? I can try to figure out where it is going weird...
>
> Here's the initrd of that particular machine:
>
> > https://people.debian.org/~glaubitz/initrd.img-5.17.0-rc5+
>
> You should be able to extract the binaries from this initrd image and the "mount" command,
> for example, should be one of the affected binaries.
I don't see anything immediately obvious here, but I'll keep looking. Is
there any way to emulate ia64? I don't see anything that'll work under
QEMU...
--
Kees Cook
Powered by blists - more mailing lists