linux-kernel - Re: linux-next: Tree for Nov 6

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

Message-ID: <20251106200541.GG1732817@nvidia.com>
Date: Thu, 6 Nov 2025 16:05:41 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: "Longia, Amandeep Kaur" <amandeepkaur.longia@....com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Vasant Hegde <vasant.hegde@....com>
Subject: Re: linux-next: Tree for Nov 6

On Thu, Nov 06, 2025 at 11:42:36AM -0800, Randy Dunlap wrote:
> > Currently, I am bisecting between kernel tags 'next-20251106' and 'next-20251105' to identify the culprit commit causing this issue.
> 
> Pretty sure that your beginning "good" should be Linux v6.18-rc4 and
> not linux-next. "bad" should be next-20251106.

Thorsten pointed this out in the morning:

https://lore.kernel.org/r/20251106185814.GA1708009@nvidia.com

Alot of bots and people have used this series before it was merged so
I'm not sure what the special condition is to trigger this.. Does the
above fix it?

Jason