From: Mark Brown <broonie@kernel.org>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: David Gow <david@davidgow.net>,
Brendan Higgins <brendan.higgins@linux.dev>,
Rae Moar <raemoar63@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Subject: Re: RCU stalls running KUnit on mainline
Date: Sat, 21 Feb 2026 14:10:25 +0000 [thread overview]
Message-ID: <aZm80VLT0ob8im-d@sirena.co.uk> (raw)
In-Reply-To: <cb63d5d8-d174-4d65-b5a3-877533f6cbd7@gtucker.io>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
On Fri, Feb 20, 2026 at 04:30:19PM +0100, Guillaume Tucker wrote:
> Yes, although I've run some automated VIXI bisections and found one
> reliable panic in rcu. I had to do it in two steps as the first
> bisection landed on a merge commit. After a bit more investigation I
> reported what I found here:
> https://lore.kernel.org/all/0150e237-41d2-40ae-a857-4f97ca664468@gtucker.io/
> I can bisect the other KUnit issues separately too if that helps now
> that I have a quick workaround to avoid this panic (see email).
Thanks for tracking that down and reporting! Hopefully it gets fixed
soon and we can turn KUnit testing back on for -next, one flaw with that
check for intermittent bugs is that it's not so easy to hold back the
tree introducing the problem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-02-21 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 14:10 RCU stalls running KUnit on mainline Mark Brown
2026-02-18 8:53 ` David Gow
2026-02-18 11:32 ` Mark Brown
2026-02-18 19:31 ` Mark Brown
2026-02-20 15:30 ` Guillaume Tucker
2026-02-21 14:10 ` Mark Brown [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=aZm80VLT0ob8im-d@sirena.co.uk \
--to=broonie@kernel.org \
--cc=brendan.higgins@linux.dev \
--cc=david@davidgow.net \
--cc=frederic@kernel.org \
--cc=gtucker@gtucker.io \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=raemoar63@gmail.com \
/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