linux-kernel - Re: [PATCH] of: Skip devicetree kunit tests when RISCV+ACPI doesn't populate root node

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <04241600-c5f7-4b49-80e0-ad4d58355623@roeck-us.net>
Date: Wed, 26 Nov 2025 07:58:17 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Rob Herring <robh@...nel.org>
Cc: Paul Walmsley <pjw@...nel.org>, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, Han Gao <rabenda.cn@...il.com>,
	linux-riscv@...ts.infradead.org
Subject: Re: [PATCH] of: Skip devicetree kunit tests when RISCV+ACPI doesn't
 populate root node

On Thu, Nov 20, 2025 at 07:06:46PM -0600, Rob Herring wrote:
> On Thu, Nov 13, 2025 at 8:53 PM Paul Walmsley <pjw@...nel.org> wrote:
> >
> > Hi Rob,
> >
> > On Wed, 12 Nov 2025, Rob Herring (Arm) wrote:
> >
> > > I guess the riscv folks don't care about supporting the relevant
> > > features either, so I've applied it. Can kicked down the road again.
> >
> > For the record: we do care.  However, it looks like this problem needs a
> > more general solution, something that applies across CPU architectures.
> > Lacking that, we might as well have behavior consistent with ARM64 - and
> > for its faults, this approach is at least simpler to reason about.
> 
> The thing is that problems show up on specific machines which has
> little to do with the specific CPU arch. I don't have any visibility
> as to what problem you all had which prompted disabling it (for the
> arch, not the kunit tests) to be able to think about a solution.
> Leaving it off just means we're potentially adding regressions in the
> future when we try to turn it on.
> 

Since the patch introducing the problem has now been backported to v6.12
and v6.17, I disabled CONFIG_OF_KUNIT_TEST for riscv entirely in my test
system.

Guenter