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: <nycvar.YFH.7.76.2410221357140.20286@cbobk.fhfr.pm>
Date: Tue, 22 Oct 2024 14:06:46 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
cc: Sasha Levin <sashal@...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 Mon, 21 Oct 2024, Paul E. McKenney wrote:

> I have to ask...
> 
> Wouldn't more people testing -next result in more pressure to fix
> linux-next problems quickly?

I believe I brought up pretty much exactly this at this year's maintainer 
summit.

>From the discussion it turned out the many people believe that this 
investing into this is probably not worth it, as it will require much more 
continous, never-ending effort (for which there are probably not enough 
resources) than just dealing with the fallout once during the -rc1+ phase.

-- 
Jiri Kosina
SUSE Labs