From: patchwork-bot+netdevbpf@kernel.org
To: Aya Levin <ayal@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, dja@axtens.net,
netdev@vger.kernel.org, moshe@mellanox.com, tariqt@nvidia.com,
dan.carpenter@oracle.com, jengelh@medozas.de, kaber@trash.net,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH net V3] net: ipv6: Validate GSO SKB before finish IPv6 processing
Date: Sat, 09 Jan 2021 22:20:07 +0000 [thread overview]
Message-ID: <161023080776.1972.10480180895140805173.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1610027418-30438-1-git-send-email-ayal@nvidia.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 7 Jan 2021 15:50:18 +0200 you wrote:
> There are cases where GSO segment's length exceeds the egress MTU:
> - Forwarding of a TCP GRO skb, when DF flag is not set.
> - Forwarding of an skb that arrived on a virtualisation interface
> (virtio-net/vhost/tap) with TSO/GSO size set by other network
> stack.
> - Local GSO skb transmitted on an NETIF_F_TSO tunnel stacked over an
> interface with a smaller MTU.
> - Arriving GRO skb (or GSO skb in a virtualised environment) that is
> bridged to a NETIF_F_TSO tunnel stacked over an interface with an
> insufficient MTU.
>
> [...]
Here is the summary with links:
- [net,V3] net: ipv6: Validate GSO SKB before finish IPv6 processing
https://git.kernel.org/netdev/net/c/b210de4f8c97
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:[~2021-01-09 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 13:50 [PATCH net V3] net: ipv6: Validate GSO SKB before finish IPv6 processing Aya Levin
2021-01-09 22:20 ` 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=161023080776.1972.10480180895140805173.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ayal@nvidia.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=dja@axtens.net \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=tariqt@nvidia.com \
--cc=yoshfuji@linux-ipv6.org \
/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;
as well as URLs for NNTP newsgroup(s).