linux-kernel - Re: [PATCH] xarray: port tests to kunit

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Z5q1mkliUUM5Xlod@casper.infradead.org>
Date: Wed, 29 Jan 2025 23:11:22 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Tamir Duberstein <tamird@...il.com>
Cc: "Liam R. Howlett" <Liam.Howlett@...cle.com>,
	Sidhartha Kumar <sidhartha.kumar@...cle.com>,
	akpm@...ux-foundation.org, christophe.leroy@...roup.eu,
	geert@...ux-m68k.org, justinstitt@...gle.com,
	linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
	linuxppc-dev@...ts.ozlabs.org, llvm@...ts.linux.dev,
	maddy@...ux.ibm.com, morbo@...gle.com, mpe@...erman.id.au,
	nathan@...nel.org, naveen@...nel.org, ndesaulniers@...gle.com,
	npiggin@...il.com, linux-mm@...ck.org
Subject: Re: [PATCH] xarray: port tests to kunit

On Wed, Jan 29, 2025 at 06:08:22PM -0500, Tamir Duberstein wrote:
> The whole point of tools is to liberate stupid humans' brains like
> mine from mundane tasks like working out who to email. The tool wasn't
> wrong; it did exactly what you told it to do in your MAINTAINERS
> entry.

Tools do get things wrong.  So do humans.  When you take your hands off
the steering wheel and the car crashes, it's still your fault.

> > > For what it's worth the kunit invocation, while obscure, is
> > > self-documenting. There's usage information that's reasonably
> > > understandable embedded in the tool itself. I looked for the userspace
> > > testing initially but failed to find
> > > tools/testing/radix-tree/xarray.c. Even now, I'm not sure how I'm
> > > meant to compile this.
> >
> > kunit is useless.  The test_xarray.c module is useless.  If you break
> > xarray, the kernel won't boot far enough to load any modules.  You
> > haven't thought about this AT ALL.
> 
> I don't understand what you're saying here.

Then I don't want to see any more patches from you until you do.