All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	kuniyu@google.com, willemb@google.com, horms@kernel.org,
	netdev@vger.kernel.org, kylebot@openai.com
Subject: Re: [PATCH net] fou: gue: check IP version of held packets for direct IP encapsulation
Date: Wed, 11 Nov 2026 00:00:07 +0000	[thread overview]
Message-ID: <179435520792.125436.7731047249946664944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106195615.2498766-1-edumazet@kernel.org>

Hello:

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

On Fri,  6 Nov 2026 20:56:15 +0100 you wrote:
> For GUE version 0, gue_gro_receive() compares the base GUE header and
> its optional fields with every held packet. For GUE version 1 (direct
> IP encapsulation), it skips this comparison and selects the next GRO
> handler only from the IP version of the incoming packet.
> 
> A held version 0 GUE packet from the same outer flow therefore stays
> eligible. For example, a GUE/IPv4/UDP packet can be aggregated with a
> direct IPv4/TCP packet, and inet_gro_receive() then parses the held
> packet's GUE header as an IPv4 header.
> 
> [...]

Here is the summary with links:
  - [net] fou: gue: check IP version of held packets for direct IP encapsulation
    https://git.kernel.org/netdev/net/c/c59f004734a2

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



      reply	other threads:[~2026-11-11  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 19:56 [PATCH net] fou: gue: check IP version of held packets for direct IP encapsulation Eric Dumazet
2026-11-11  0:00 ` patchwork-bot+netdevbpf [this message]

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=179435520792.125436.7731047249946664944.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=kylebot@openai.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.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.