linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	"Anthony Yznaga <anthony.yznaga"@oracle.com,
	Kees Cook <keescook@chromium.org>
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: Wed, 2 Mar 2022 13:35:54 +0100	[thread overview]
Message-ID: <09fd50e3-7483-41ec-ee71-1a2ce8ff7b0f@leemhuis.info> (raw)
In-Reply-To: <ed02afd1-4e0f-4604-324c-0a58c0ca4b57@physik.fu-berlin.de>

On 02.03.22 13:01, John Paul Adrian Glaubitz wrote:
> On 2/20/22 18:12, Thorsten Leemhuis wrote:
>> I noticed a regression report in bugzilla.kernel.org that afaics nobody
>> acted upon since it was reported about a week ago, that's why I'm hereby
>> forwarding it to the lists and the relevant people. To quote
>> https://bugzilla.kernel.org/show_bug.cgi?id=215601 :
> As a heads-up, this issue has been fixed in 439a8468242b [1].
> 
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=439a8468242b313486e69b8cc3b45ddcfa898fbf

Thx, but no need to in this particular, thx to the "Link:
https://lore.kernel.org/r/a3edd529-c42d-3b09-135c-7e98a15b150f@leemhuis.info"
that Kees included in the patch description. That allowed regzbot to
automatically notice the two new mailing lists threads where Kees posted
patches for testing and later also made regzbot notice the fix when it
landed in mainline:
https://linux-regtracking.leemhuis.info/regzbot/regression/a3edd529-c42d-3b09-135c-7e98a15b150f@leemhuis.info/

Sadly quite a few developers don't set such links tags, but I hope with
some education (and a improved regzbot that is a bit more useful at
least for subsystem maintainers) that will improve over time.

Ciao, Thorsten

      reply	other threads:[~2022-03-02 12:36 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
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 [this message]

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=09fd50e3-7483-41ec-ee71-1a2ce8ff7b0f@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc="Anthony Yznaga <anthony.yznaga"@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --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@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).