All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Ramaseuski <jramaseu@redhat.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, horms@kernel.org,
	pabeni@redhat.com, edumazet@google.com, sdf@fomichev.me,
	ahmed.zaki@intel.com, aleksander.lobakin@intel.com,
	benoit.monin@gmx.fr, willemb@google.com, tizhao@redhat.com,
	mschmidt@redhat.com, willemdebruijn.kernel@gmail.com
Subject: Re: [PATCH net v3] net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM
Date: Tue, 19 Aug 2025 00:30:05 +0000	[thread overview]
Message-ID: <175556340575.2959470.8995178513415785744.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250814105119.1525687-1-jramaseu@redhat.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 14 Aug 2025 12:51:19 +0200 you wrote:
> When performing Generic Segmentation Offload (GSO) on an IPv6 packet that
> contains extension headers, the kernel incorrectly requests checksum offload
> if the egress device only advertises NETIF_F_IPV6_CSUM feature, which has
> a strict contract: it supports checksum offload only for plain TCP or UDP
> over IPv6 and explicitly does not support packets with extension headers.
> The current GSO logic violates this contract by failing to disable the feature
> for packets with extension headers, such as those used in GREoIPv6 tunnels.
> 
> [...]

Here is the summary with links:
  - [net,v3] net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM
    https://git.kernel.org/netdev/net/c/864e3396976e

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



  parent reply	other threads:[~2025-08-19  0:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 10:51 [PATCH net v3] net: gso: Forbid IPv6 TSO with extensions on devices with only IPV6_CSUM Jakub Ramaseuski
2025-08-14 13:11 ` Willem de Bruijn
2025-08-19  0:30 ` patchwork-bot+netdevbpf [this message]
2026-03-05  7:42 ` xietangxin
2026-03-05 14:57   ` Willem de Bruijn
2026-03-05 15:21     ` Paolo Abeni
2026-03-06  6:32       ` xietangxin
2026-03-06  8:29         ` Paolo Abeni
2026-03-14 16:19           ` Willem de Bruijn
2026-03-16  8:38             ` Paolo Abeni
2026-03-16 16:55               ` Willem de Bruijn
2026-03-20  9:38             ` xietangxin
2026-03-20 19:03               ` Willem de Bruijn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=175556340575.2959470.8995178513415785744.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ahmed.zaki@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=benoit.monin@gmx.fr \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jramaseu@redhat.com \
    --cc=kuba@kernel.org \
    --cc=mschmidt@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=tizhao@redhat.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.