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: <20250730181835.2423917b@kernel.org>
Date: Wed, 30 Jul 2025 18:18:35 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jason Wang <jasowang@...hat.com>
Cc: Cindy Lu <lulu@...hat.com>, "K. Y. Srinivasan" <kys@...rosoft.com>,
 Haiyang Zhang <haiyangz@...rosoft.com>, Wei Liu <wei.liu@...nel.org>,
 Dexuan Cui <decui@...rosoft.com>, Andrew Lunn <andrew+netdev@...n.ch>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet
 <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Simon Horman
 <horms@...nel.org>, Michael Kelley <mhklinux@...look.com>, Shradha Gupta
 <shradhagupta@...ux.microsoft.com>, Kees Cook <kees@...nel.org>, Stanislav
 Fomichev <sdf@...ichev.me>, Kuniyuki Iwashima <kuniyu@...gle.com>,
 Alexander Lobakin <aleksander.lobakin@...el.com>, Guillaume Nault
 <gnault@...hat.com>, Joe Damato <jdamato@...tly.com>, Ahmed Zaki
 <ahmed.zaki@...el.com>, "open list:Hyper-V/Azure CORE AND DRIVERS"
 <linux-hyperv@...r.kernel.org>, "open list:NETWORKING DRIVERS"
 <netdev@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND] netvsc: transfer lower device max tso size

On Thu, 31 Jul 2025 09:07:27 +0800 Jason Wang wrote:
> > > Btw, if I understand this correctly. This is for future development so
> > > it's not a blocker for this patch?  
> >
> > Not a blocker, I'm just giving an example of the netvsc auto-weirdness
> > being a source of tech debt and bugs. Commit d7501e076d859d is another
> > recent one off the top of my head. IIUC systemd-networkd is broadly
> > deployed now. It'd be great if there was some migration plan for moving
> > this sort of VM auto-bonding to user space (with the use of the common
> > bonding driver, not each hypervisor rolling its own).
> >  
> 
> Please let me know if you want to merge this patch or not. If not, how
> to proceed.

As is its definitely not getting merged.
Please make it look less burdensome or fix it in user space(!!).

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ