From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux PA-RISC Mailing List <linux-parisc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam James <sam@gentoo.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Bisected stability regression in 6.6
Date: Wed, 22 Nov 2023 10:07:09 +0100 [thread overview]
Message-ID: <8b1cc069-b395-401a-aeff-85dd0c1cd8b0@leemhuis.info> (raw)
In-Reply-To: <ZU8nGV4sg-l9-pkf@archie.me>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 11.11.23 08:02, Bagas Sanjaya wrote:
> On Sat, Nov 11, 2023 at 01:31:01AM -0500, matoro wrote:
>> Hi Helge, I have bisected a regression in 6.6 which is causing userspace
>> segfaults at a significantly increased rate in kernel 6.6.
> #regzbot ^introduced: 3033cd4307681c
#regzbot fix: 5f74f820f6fc844b95f9
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2023-11-22 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 6:31 Bisected stability regression in 6.6 matoro
2023-11-11 7:02 ` Bagas Sanjaya
2023-11-22 9:07 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
2023-11-11 21:21 ` Helge Deller
2023-11-11 21:27 ` Sam James
2023-11-11 23:33 ` matoro
2023-11-12 1:22 ` Dr. David Alan Gilbert
2023-11-12 8:03 ` Helge Deller
2023-11-12 12:07 ` Dr. David Alan Gilbert
2023-11-12 20:22 ` Helge Deller
2023-11-12 23:37 ` matoro
2023-11-11 21:28 ` matoro
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=8b1cc069-b395-401a-aeff-85dd0c1cd8b0@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sam@gentoo.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).