linux-kernel - Re: linus-next: improving functional testing for to-be-merged pull requests

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <7c66ff8d-f139-4cf7-b477-d0179c62f922@paulmck-laptop>
Date: Wed, 23 Oct 2024 13:22:45 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Christoph Hellwig <hch@...radead.org>, Sasha Levin <sashal@...nel.org>,
	Kees Cook <kees@...nel.org>, ksummit@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: linus-next: improving functional testing for to-be-merged pull
 requests

On Wed, Oct 23, 2024 at 12:24:05PM -0700, Linus Torvalds wrote:
> On Wed, 23 Oct 2024 at 11:37, Paul E. McKenney <paulmck@...nel.org> wrote:
> >
> > Functional testing?
> 
> Yes. Things like the stuff that Guenter does every -rc, and that
> invariably finds several issues every single merge window.
> 
> Like actually booting up the kernel on multiple different odd
> architectures. But also much more complex things than just running a
> torture test for a very small piece of the kernel.
> 
> The same way linux-next does the build testing on many different
> architectures, and that often finds things that developers missed
> simply because the bulk of developers are still purely on x86-64.

Fair point, my testing is still strictly x86-64.

							Thanx, Paul