netdev - Re: [PATCH net-next v2 0/2] Lift UDP_SEGMENT restriction for egress via device w/o csum offload

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: 
 <171962585710.15618.2691302964178977119.git-patchwork-notify@kernel.org>
Date: Sat, 29 Jun 2024 01:50:57 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Sitnicki <jakub@...udflare.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
 kuba@...nel.org, pabeni@...hat.com, willemb@...gle.com,
 kernel-team@...udflare.com
Subject: Re: [PATCH net-next v2 0/2] Lift UDP_SEGMENT restriction for egress
 via device w/o csum offload

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Wed, 26 Jun 2024 19:51:25 +0200 you wrote:
> This is a follow-up to an earlier question [1] if we can make UDP GSO work with
> any egress device, even those with no checksum offload capability. That's the
> default setup for TUN/TAP.
> 
> Because there is a change in behavior - sendmsg() does no longer return EIO
> error - I'm submitting through net-next tree, rather than net, as per Willem's
> advice.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] udp: Allow GSO transmit from devices with no checksum offload
    https://git.kernel.org/netdev/net-next/c/10154dbded6d
  - [net-next,v2,2/2] selftests/net: Add test coverage for UDP GSO software fallback
    https://git.kernel.org/netdev/net-next/c/3e400219c04d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html