From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?Wmhhb3BpbmcgU2h1ICjoiJLlj6zlubMpIDx6aGFvcGluZy5zaHVAbWVkaWF0ZWsu?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
=?utf-8?b?Y29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: edumazet@google.com, ncardwell@google.com, kuniyu@google.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, dsahern@kernel.org,
willemb@google.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, haijun.liu@mediatek.com,
xiayu.zhang@mediatek.com, lambert.wang@mediatek.com,
Iven.Yang@mediatek.com, nbd@nbd.name, hw.he@mediatek.com
Subject: Re: [PATCH net v5] net: gro: Fix nesting of TCP GSO SKBs in skb_gro_receive_list()
Date: Thu, 03 Sep 2026 10:30:06 +0000 [thread overview]
Message-ID: <178843140634.3256648.8035373141485573563.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260901082312.14596-1-zhaoping.shu@mediatek.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 1 Sep 2026 16:23:12 +0800 you wrote:
> From: HW He <hw.he@mediatek.com>
>
> Fraglist GRO and hardware GRO can create an fraglist of
> HW-GRO packets. This cannot be segmented back into
> the original form on TCP tethering scenario.
>
> Avoid constructing such a GSO packet, by flushing an already
> built fraglist GRO packet if a hardware GRO packet arrives.
>
> [...]
Here is the summary with links:
- [net,v5] net: gro: Fix nesting of TCP GSO SKBs in skb_gro_receive_list()
https://git.kernel.org/netdev/net/c/66817a979426
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-03 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 8:23 [PATCH net v5] net: gro: Fix nesting of TCP GSO SKBs in skb_gro_receive_list() zhaoping.shu
2026-09-01 14:11 ` Willem de Bruijn
2026-09-03 10:30 ` 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=178843140634.3256648.8035373141485573563.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?Wmhhb3BpbmcgU2h1ICjoiJLlj6zlubMpIDx6aGFvcGluZy5zaHVAbWVkaWF0ZWsu?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc==?utf-8?b?Y29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=Iven.Yang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=haijun.liu@mediatek.com \
--cc=horms@kernel.org \
--cc=hw.he@mediatek.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=lambert.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=xiayu.zhang@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox