From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Kees Cook <keescook@chromium.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Anthony Yznaga <anthony.yznaga@oracle.com>
Cc: 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: Mon, 21 Feb 2022 20:49:20 +0100 [thread overview]
Message-ID: <94c3be49-0262-c613-e5f5-49b536985dde@physik.fu-berlin.de> (raw)
In-Reply-To: <03497313-A472-4152-BD28-41C35E4E824E@chromium.org>
Hi Kees!
On 2/21/22 08:42, Kees Cook wrote:
>>>> Reverting this commit resolves the issue up to and including git tip,
>>>> with no (visible) issues.
>>>>
>>>> Hardware: HP Integrity rx2800 i2 Kernel config attached.
>>>
>>> Could somebody take a look into this? Or was this discussed somewhere
>>> else already? Or even fixed?
>>>
>>> Anyway, to get this tracked:
>>>
>>> #regzbot introduced: 5f501d555653f8968011a1e65ebb121c8b43c144
>>> #regzbot from: matoro <matoro_bugzilla_kernel@matoro.tk>
>>> #regzbot title: gcc segv at startup on ia64
>>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215601
>
> Does this fix it?
>
> https://www.ozlabs.org/~akpm/mmotm/broken-out/elf-fix-overflow-in-total-mapping-size-calculation.patch
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.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
WARNING: multiple messages have this Message-ID (diff)
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Kees Cook <keescook@chromium.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Anthony Yznaga <anthony.yznaga@oracle.com>
Cc: 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: Mon, 21 Feb 2022 19:49:20 +0000 [thread overview]
Message-ID: <94c3be49-0262-c613-e5f5-49b536985dde@physik.fu-berlin.de> (raw)
In-Reply-To: <03497313-A472-4152-BD28-41C35E4E824E@chromium.org>
Hi Kees!
On 2/21/22 08:42, Kees Cook wrote:
>>>> Reverting this commit resolves the issue up to and including git tip,
>>>> with no (visible) issues.
>>>>
>>>> Hardware: HP Integrity rx2800 i2 Kernel config attached.
>>>
>>> Could somebody take a look into this? Or was this discussed somewhere
>>> else already? Or even fixed?
>>>
>>> Anyway, to get this tracked:
>>>
>>> #regzbot introduced: 5f501d555653f8968011a1e65ebb121c8b43c144
>>> #regzbot from: matoro <matoro_bugzilla_kernel@matoro.tk>
>>> #regzbot title: gcc segv at startup on ia64
>>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id!5601
>
> Does this fix it?
>
> https://www.ozlabs.org/~akpm/mmotm/broken-out/elf-fix-overflow-in-total-mapping-size-calculation.patch
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.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2022-02-21 19:53 UTC|newest]
Thread overview: 32+ 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:12 ` Thorsten Leemhuis
2022-02-20 17:19 ` Thorsten Leemhuis
2022-02-20 17:19 ` Thorsten Leemhuis
2022-02-21 7:42 ` Kees Cook
2022-02-21 7:42 ` Kees Cook
2022-02-21 19:49 ` John Paul Adrian Glaubitz [this message]
2022-02-21 19:49 ` John Paul Adrian Glaubitz
2022-02-21 20:58 ` Kees Cook
2022-02-21 20:58 ` Kees Cook
2022-02-21 21:57 ` John Paul Adrian Glaubitz
2022-02-21 21:57 ` John Paul Adrian Glaubitz
2022-02-24 3:58 ` Kees Cook
2022-02-24 3:58 ` Kees Cook
2022-02-24 5:16 ` Kees Cook
2022-02-24 5:16 ` Kees Cook
2022-02-24 9:33 ` John Paul Adrian Glaubitz
2022-02-24 9:33 ` John Paul Adrian Glaubitz
2022-02-24 14:22 ` matoro
2022-02-24 14:22 ` matoro
2022-02-24 16:33 ` Kees Cook
2022-02-24 16:33 ` Kees Cook
2022-02-26 11:52 ` Kees Cook
2022-02-26 11:52 ` Kees Cook
2022-02-28 10:46 ` Magnus Groß
2022-02-28 10:46 ` Magnus Groß
2022-02-28 20:41 ` Kees Cook
2022-02-28 20:41 ` Kees Cook
2022-03-02 12:01 ` John Paul Adrian Glaubitz
2022-03-02 12:01 ` John Paul Adrian Glaubitz
2022-03-02 12:35 ` Thorsten Leemhuis
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=94c3be49-0262-c613-e5f5-49b536985dde@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=anthony.yznaga@oracle.com \
--cc=keescook@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.