linux-kernel - Re: [REGRESSION] - BROKEN NETWORKING Re: Linux 6.16.3

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: <20250824185526.GA958@1wt.eu>
Date: Sun, 24 Aug 2025 20:55:26 +0200
From: Willy Tarreau <w@....eu>
To: Kyle Sanderson <kyle.leet@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
        torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
        jslaby@...e.cz
Subject: Re: [REGRESSION] - BROKEN NETWORKING Re: Linux 6.16.3

Hello,

On Sun, Aug 24, 2025 at 11:31:01AM -0700, Kyle Sanderson wrote:
> Thanks for maintaining these as always. For the first time in a long time, I
> booted the latest stable (6.15.x -> 6.16.3) and somehow lost my networking.
> It looks like there is a patch from Intel (reported by AMD) that did not
> make it into stable 6.16.
> 
> e67a0bc3ed4fd8ee1697cb6d937e2b294ec13b5e - ixgbe
> https://lore.kernel.org/all/94d7d5c0bb4fc171154ccff36e85261a9f186923.1755661118.git.calvin@wbinvd.org/
> - i40e

Your description is very confusing. First you indicate in the subject
that there is a regression in 6.16.3 (implying from 6.16.2 then), and
you describe a 6.15.x to 6.16.x upgrade, which then has nothing to do
with 6.16.x alone but much more likely with 6.15 to 6.16. Or did a
previous 6.16 work fine ? Also the patch you pointed above is neither
in 6.15 nor in 6.16, so it's not just "missing from 6.16".

Based on your links and descriptions above I suspect that instead it's a
6.15 to 6.16 regression that was brought by a0285236ab93 and that commit
e67a0bc3ed4fd above fixed it in 6.17-rc2, is that it ? If so, can you
apply that patch to confirm that it works and is desired in 6.16.x ?

Regards,
Willy