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: <1e89542d-6f9e-4e85-8292-ebb49091433a@sirena.org.uk>
Date: Tue, 22 Oct 2024 12:50:50 +0100
From: Mark Brown <broonie@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Christoph Hellwig <hch@...radead.org>, Kees Cook <kees@...nel.org>,
	torvalds@...ux-foundation.org, ksummit@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: linus-next: improving functional testing for to-be-merged pull
 requests

On Tue, Oct 22, 2024 at 06:52:51AM -0400, Sasha Levin wrote:
> On Mon, Oct 21, 2024 at 11:48:34PM -0700, Christoph Hellwig wrote:

> The script tripped on the very first PR it looked at:
> https://lore.kernel.org/all/20241021171728.274997-1-pbonzini@redhat.com/

> And in particular, this commit: afa9b48f327c ("KVM: arm64: Shave a few
> bytes from the EL2 idmap code")

> (sorry, not trying to pick on anyone/anything, just an example...)

> The commit can't be found on lore.kernel.org, it was never in -next, and
> yet Linus pulled it promptly without questioning anything.

That was on the list at least, but buried in the replies to a thread
rather than posted separately:

  https://lore.kernel.org/86msjc56mi.wl-maz@kernel.org

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)