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: <20241031151943.7be1cf5c@gandalf.local.home>
Date: Thu, 31 Oct 2024 15:19:43 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, Christoph Hellwig
 <hch@...radead.org>, Kees Cook <kees@...nel.org>, 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 Thu, 31 Oct 2024 13:08:12 -0600
Shuah Khan <skhan@...uxfoundation.org> wrote:

> > But pushing to linux-next for a day or two, what does that give me?
> >   
> 
> I don't send pull requests without soaking it in next for 2 to 3 days.
> It helps me find problems related to things something breaking on an
> architecture and/or config.
> 
> I find next very helpful in finding merge conflicts and build/test
> breakages.

I have a 13 hour test suite that I run before pushing anything. And since
it's going into the rc release, any merge conflict that happens in next is
likely something that isn't even applicable for Linus's tree. Sure, it will
need to be addressed in the next merge window, but that would have been
found after getting in Linus's tree anyway, because really a fix to Linus's
tree should have no merge conflicts.

-- Steve