All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Kees Cook <keescook@chromium.org>
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: Thu, 24 Feb 2022 10:33:20 +0100	[thread overview]
Message-ID: <7e3a93e7-1300-8460-30fb-789180a745eb@physik.fu-berlin.de> (raw)
In-Reply-To: <202202232030.B408F0E895@keescook>

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@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>
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: Thu, 24 Feb 2022 09:33:20 +0000	[thread overview]
Message-ID: <7e3a93e7-1300-8460-30fb-789180a745eb@physik.fu-berlin.de> (raw)
In-Reply-To: <202202232030.B408F0E895@keescook>

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@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2022-02-24  9:33 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
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 [this message]
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=7e3a93e7-1300-8460-30fb-789180a745eb@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.