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: <2025082529-reporter-frays-73a5@gregkh>
Date: Mon, 25 Aug 2025 09:00:14 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Kyle Sanderson <kyle.leet@...il.com>
Cc: 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

On Sun, Aug 24, 2025 at 11:31:01AM -0700, Kyle Sanderson wrote:
> On 8/23/2025 7:51 AM, Greg Kroah-Hartman wrote:
> > I'm announcing the release of the 6.16.3 kernel.
> > 
> > All users of the 6.16 kernel series that use the ext4 filesystem should
> > upgrade.
> > 
> > The updated 6.16.y git tree can be found at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.16.y
> > and can be browsed at the normal kernel.org git web browser:
> > 	https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> > 
> > thanks,
> > 
> > greg k-h
> 
> Hi Greg,
> 
> 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

Any specific reason why this hasn't been asked to be backported to
stable trees if it fixes an issue?   Please cc: the developers involved
so that they know to let us pick it up.

thanks,

greg k-h