linux-kernel - Re: [GIT PULL] Networking for v6.17

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: <CAHk-=wjKh8X4PT_mU1kD4GQrbjivMfPn-_hXa6han_BTDcXddw@mail.gmail.com>
Date: Tue, 5 Aug 2025 19:22:48 +0300
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, 
	pabeni@...hat.com
Subject: Re: [GIT PULL] Networking for v6.17

On Sun, 27 Jul 2025 at 04:35, Jakub Kicinski <kuba@...nel.org> wrote:
>
> Networking changes for 6.17.

So I found out the hard way while traveling that this networking pull
seems to have broken USB tethering for me. Which I only use when
traveling, but then I do often end up relying on my phone as the
source of internet (the phone being on the single-device flight wifi,
and tethering to the laptop which is why hotspot doesn't necessarily
work).

It *might* be something else, and I'm bisecting it right now, but the
networking pull is the obvious first suspect, and my first three
bisection steps have taken me into that pull.

It could still jump out of that pull - there are non-networking
changes still in the pile left to be bisected, but I'd be honestly
surprised if it does.

This is very standard usbnet with cdc_ether/ncm/wdm/mbim.

A failing kernel will find the device and talk about it, but then it
never gets configured and you never get any actual networking.

Any obvious suspects I should look for?

           Linus