All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	horms@kernel.org, maxk@qualcomm.com, rusty@rustcorp.com.au
Subject: Re: [PATCH net] inet: frags: strip GSO state from fragments before reassembly
Date: Thu, 27 Aug 2026 20:00:15 +0000	[thread overview]
Message-ID: <178786081564.1822702.16249918450041768118.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <937926e509f2acd8e0e66520dc2b30fd6b4d1687.1787839506.git.pabeni@redhat.com>

Hello:

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

On Thu, 27 Aug 2026 16:07:07 +0200 you wrote:
> From: Xinyang Ge <xinyang@anthropic.com>
> 
> A virtio_net_hdr (tun/tap, or AF_PACKET with PACKET_VNET_HDR) can mark
> an IPv4 or IPv6 fragment as GSO; nothing relates gso_type to frag_off.
> inet_frag_reasm_prepare()/inet_frag_reasm_finish() keep the first
> fragment's skb as the head of the reassembled datagram, including its
> shinfo->gso_size/gso_type/gso_segs, and chain the remaining fragments
> on frag_list with whatever linear/paged layout they arrived with.
> 
> [...]

Here is the summary with links:
  - [net] inet: frags: strip GSO state from fragments before reassembly
    https://git.kernel.org/netdev/net/c/d5dc1e69fd72

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



      parent reply	other threads:[~2026-08-27 20:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 14:07 [PATCH net] inet: frags: strip GSO state from fragments before reassembly Paolo Abeni
2026-08-27 14:34 ` Eric Dumazet
2026-08-27 20: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=178786081564.1822702.16249918450041768118.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rusty@rustcorp.com.au \
    /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.