[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e3a93e7-1300-8460-30fb-789180a745eb@physik.fu-berlin.de>
Date: Thu, 24 Feb 2022 10:33:20 +0100
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Kees Cook <keescook@...omium.org>
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
Hi Kees!
On 2/24/22 06:16, Kees Cook wrote:
>> 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.
>
> In dmesg, do you see any of these reports?
>
> pr_info("%d (%s): Uhuuh, elf segment at %px requested but the memory is mapped already\n",
> task_pid_nr(current), current->comm, (void *)addr);
I'll check that.
> I don't see anything out of order in the "mount" binary from the above
> initrd. What does "readelf -lW" show for the GCC you're seeing failures
> on?
I'm not 100% sure whether it's the mount binary that is affected. What happens is that once init takes over,
I'm seeing multiple "Segmentation Fault" message on the console until I'm dropped to the initrd shell.
I can check what dmesg says.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@...ian.org
`. `' Freie Universitaet Berlin - glaubitz@...sik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists