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: <Zxe65Zu3GRdwzXjo@sashalap>
Date: Tue, 22 Oct 2024 10:47:01 -0400
From: Sasha Levin <sashal@...nel.org>
To: Mark Brown <broonie@...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 12:50:50PM +0100, Mark Brown wrote:
>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

If folks are interested in collaborating around -next analysis and maybe
adding a bot/dashboard/etc, I've pushed my scripts to
https://git.kernel.org/pub/scm/linux/kernel/git/sashal/next-analysis.git/

Right now they're enough to generate a histogram showing how many
patches spent N days in -next:

$ git log --format="%H" --no-merges origin/master..next/master | shuf | head -n500 | xargs histo.sh ~/next-analysis/db/
Days in -next:
----------------------------------------
  0  |
  1  | ████████████████████ (40)
  2  | ███████████████████████████████ (62)
  3  | █████████████ (27)
  4  | █████████████ (27)
  5  | ███████████████████ (39)
  6  | ██████████████ (28)
  7  | ████████ (16)
  8  | ██████████████████ (37)
  9  | ██████ (12)
10  | █████████████████████ (42)
11  | █████████████████████████ (50)
12  | ██████ (12)
13  | █████ (10)
14+ | █████████████████████████████████████████████████ (98)

As well as find commits that did not appear on lore:

$ git log --format="%H" --no-merges origin/master..next/master | shuf | head -n100 | xargs no-lore.sh ~/next-analysis/db/
c88414f56c37f XArray: Prevent node leaks in xas_alloc()

-- 
Thanks,
Sasha