From: Frederic Weisbecker <frederic@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Waiman Long <longman@redhat.com>,
Marco Crivellari <marco.crivellari@suse.com>,
Michal Hocko <mhocko@suse.com>,
Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [CRASH] kunit failures in platform-device-devm
Date: Tue, 3 Mar 2026 01:50:30 +0100 [thread overview]
Message-ID: <aaYwVseQBPiJDA0M@pavilion.home> (raw)
In-Reply-To: <aaWtcMpwHUt9E5bD@google.com>
Le Mon, Mar 02, 2026 at 03:32:00PM +0000, Alice Ryhl a écrit :
> On Sun, Mar 01, 2026 at 02:06:49PM +0000, Alice Ryhl wrote:
> > Hi DRIVER CORE, KOBJECTS, DEBUGFS AND SYSFS,
> >
> > I've experienced a fair number of different crashes when running kunit
> > locally. I just ran this command on v7.0-rc1 or upstream/master:
> >
> > ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --arch x86_64 --kconfig_add CONFIG_RUST=y --kconfig_add CONFIG_PCI=y
>
> Bisection has been carried out!
>
> The culprit is commit 5564c12385b7 ("kthread: Include unbound kthreads
> in the managed affinity list"). Cc'ing everyone from this commit.
>
> On this commit, kunit (executed using above command) crashes for me 70%
> of the time (14 out of 20 runs) with kernel crashes (Oops) and
> refcount_t use-after-free warnings in pm_runtime_test_cases and
> platform-device-devm. On the parent commit, I was able to run kunit 24
> times in a row with zero kunit failures.
>
> The same crashes occur on tag v7.0-rc2, so this issue is not fixed.
I can reproduce (though rather 10% of the time). Investigating...
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2026-03-03 0:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 14:06 [CRASH] kunit failures in platform-device-devm Alice Ryhl
2026-03-01 20:17 ` Greg Kroah-Hartman
2026-03-01 21:21 ` Alice Ryhl
2026-03-02 12:31 ` Sasha Levin
2026-03-02 15:32 ` Alice Ryhl
2026-03-03 0:45 ` David Gow
2026-03-03 10:00 ` Alice Ryhl
2026-03-03 10:32 ` Frederic Weisbecker
2026-03-03 0:50 ` Frederic Weisbecker [this message]
2026-03-02 15:52 ` Alice Ryhl
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=aaYwVseQBPiJDA0M@pavilion.home \
--to=frederic@kernel.org \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
/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