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: <1dda44c4-b199-4c41-8c9f-f08247b7f5eb@amd.com>
Date: Sun, 9 Nov 2025 14:28:56 +0530
From: "Longia, Amandeep Kaur" <AmandeepKaur.Longia@....com>
To: Jason Gunthorpe <jgg@...dia.com>, Randy Dunlap <rdunlap@...radead.org>
Cc: 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 11/7/2025 1:35 AM, Jason Gunthorpe wrote:
> 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

Applying the patch available at 
https://lore.kernel.org/all/20251107104701.237041-1-joro@8bytes.org 
resolves the build issue.

Thanks,
Amandeep Kaur