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: <6ea4bd33-180b-4b03-9108-6b316b10fd13@iogearbox.net>
Date: Tue, 24 Sep 2024 09:03:04 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: netdev@...r.kernel.org
Cc: edumazet@...gle.com, pabeni@...hat.com
Subject: Re: [PATCH net 2/2] net: Fix gso_features_check to check for both
 dev->gso_{ipv4_,}max_size

On 9/23/24 11:22 PM, Daniel Borkmann wrote:

> Commit 24ab059d2ebd ("net: check dev->gso_max_size in gso_features_check()")
> added a dev->gso_max_size test to gso_features_check() in order to fall
> back to GSO when needed.
>
> This was added as it was noticed that some drivers could misbehave if TSO
> packets get too big. However, the check doesn't respect dev->gso_ipv4_max_size
> limit. For instance, a device could be configured with BIG TCP for IPv4,
> but not IPv6.
>
> Therefore, add a netif_get_gso_max_size() equivalent to netif_get_gro_max_size()
> and use the helper to respect both limits before falling back to GSO engine.
>
> Fixes: 24ab059d2ebd ("net: check dev->gso_max_size in gso_features_check()")
> Signed-off-by: Daniel Borkmann <daniel@...earbox.net>
> Cc: Eric Dumazet <edumazet@...gle.com>
> Cc: Paolo Abeni <pabeni@...hat.com>

(Sorry, Cc got missed due to config issue as I recently switched to a

new machine.)


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ