From: Kees Cook <keescook@chromium.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Anthony Yznaga <anthony.yznaga@oracle.com>,
matoro_bugzilla_kernel@matoro.tk,
Andrew Morton <akpm@linux-foundation.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
linux-ia64@vger.kernel.org,
Linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: regression: Bug 215601 - gcc segv at startup on ia64
Date: Wed, 23 Feb 2022 19:58:58 -0800 [thread overview]
Message-ID: <202202231957.801F1780@keescook> (raw)
In-Reply-To: <4e42e754-d87e-5f6b-90db-39b4700ee0f1@physik.fu-berlin.de>
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
next prev parent reply other threads:[~2022-02-24 3:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 17:12 regression: Bug 215601 - gcc segv at startup on ia64 Thorsten Leemhuis
2022-02-20 17:19 ` Thorsten Leemhuis
2022-02-21 7:42 ` Kees Cook
2022-02-21 19:49 ` John Paul Adrian Glaubitz
2022-02-21 20:58 ` Kees Cook
2022-02-21 21:57 ` John Paul Adrian Glaubitz
2022-02-24 3:58 ` Kees Cook [this message]
2022-02-24 5:16 ` Kees Cook
2022-02-24 9:33 ` John Paul Adrian Glaubitz
2022-02-24 14:22 ` matoro
2022-02-24 16:33 ` Kees Cook
2022-02-26 11:52 ` Kees Cook
2022-02-28 10:46 ` Magnus Groß
2022-02-28 20:41 ` Kees Cook
2022-03-02 12:01 ` John Paul Adrian Glaubitz
2022-03-02 12:35 ` Thorsten Leemhuis
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=202202231957.801F1780@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=anthony.yznaga@oracle.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matoro_bugzilla_kernel@matoro.tk \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).