From: "Linux regression tracking #adding (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Guenter Roeck <linux@roeck-us.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: Linux 6.3-rc2
Date: Sun, 19 Mar 2023 15:06:55 +0100 [thread overview]
Message-ID: <73b7867a-8a1f-d521-d290-77bc7fcb2226@leemhuis.info> (raw)
In-Reply-To: <d915df60-d06b-47d4-8b47-8aa1bbc2aac7@roeck-us.net>
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
On 13.03.23 16:53, Guenter Roeck wrote:
> On Sun, Mar 12, 2023 at 04:45:57PM -0700, Linus Torvalds wrote:
>
> Runtime:
>
> Warning backtraces in calls from ct_nmi_enter(),
> seen randomly.
>
I had expected this would be quickly resolved, but as the fix is not yet
heading towards mainline, lets better ensure this regression is tracked:
#regzbot ^introduced 62b95a7b44d1
#regzbot title arm: vfp: random Warning backtraces in calls from
ct_nmi_enter()
#regzbot fix: ARM: vfp: Fix broken softirq handling with instrumentation
enabled
#regzbot ignore-activity
FWIW, latest patchset to fix it afaics is here:
https://lore.kernel.org/all/20230316082007.652669-1-ardb@kernel.org/
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-03-19 14:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 23:45 Linux 6.3-rc2 Linus Torvalds
2023-03-13 8:11 ` Build regressions/improvements in v6.3-rc2 Geert Uytterhoeven
2023-03-13 8:16 ` Geert Uytterhoeven
2023-03-13 9:08 ` HID: Stable backport request (all viable versions) Lee Jones
2023-03-13 10:51 ` Greg KH
2023-03-13 15:53 ` Linux 6.3-rc2 Guenter Roeck
2023-03-13 18:21 ` Linus Torvalds
2023-03-13 20:30 ` Guenter Roeck
2023-03-13 22:16 ` Linus Torvalds
2023-03-13 22:49 ` Guenter Roeck
2023-03-13 23:11 ` Frederic Weisbecker
2023-03-13 23:17 ` Linus Torvalds
2023-03-13 23:25 ` Frederic Weisbecker
2023-03-14 0:52 ` Guenter Roeck
2023-03-14 11:18 ` Frederic Weisbecker
2023-03-14 11:40 ` Peter Zijlstra
2023-03-14 12:01 ` Ard Biesheuvel
2023-03-14 12:27 ` Peter Zijlstra
2023-03-14 14:40 ` Guenter Roeck
2023-03-14 16:16 ` Guenter Roeck
2023-03-19 14:06 ` Linux regression tracking #adding (Thorsten Leemhuis) [this message]
2023-04-14 14:11 ` Linux regression tracking #update (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=73b7867a-8a1f-d521-d290-77bc7fcb2226@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.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 NNTP newsgroup(s).