All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: matoro <matoro_mailinglist_kernel@matoro.tk>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	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, 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 08:33:43 -0800	[thread overview]
Message-ID: <202202240832.F40AEB20@keescook> (raw)
In-Reply-To: <65ed8ab4fad779fadf572fb737dfb789@matoro.tk>

On Thu, Feb 24, 2022 at 09:22:04AM -0500, matoro wrote:
> Hi Kees, I can provide live ssh access to my system exhibiting the issue.
> My system is a lot more stable due to using openrc rather than systemd, for
> me GCC seems to be the only binary affected.  Would that be helpful?

Yeah, that might be helpful. I have access to a Debian ia64 porter box,
but it's not running the broken kernel, so I can only examine "normal"
behavior.

I'll switch to off-list email...

-Kees

-- 
Kees Cook

WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: matoro <matoro_mailinglist_kernel@matoro.tk>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	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, 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 16:33:43 +0000	[thread overview]
Message-ID: <202202240832.F40AEB20@keescook> (raw)
In-Reply-To: <65ed8ab4fad779fadf572fb737dfb789@matoro.tk>

On Thu, Feb 24, 2022 at 09:22:04AM -0500, matoro wrote:
> Hi Kees, I can provide live ssh access to my system exhibiting the issue.
> My system is a lot more stable due to using openrc rather than systemd, for
> me GCC seems to be the only binary affected.  Would that be helpful?

Yeah, that might be helpful. I have access to a Debian ia64 porter box,
but it's not running the broken kernel, so I can only examine "normal"
behavior.

I'll switch to off-list email...

-Kees

-- 
Kees Cook

  reply	other threads:[~2022-02-24 16: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
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 [this message]
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=202202240832.F40AEB20@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=matoro_mailinglist_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.