From: patchwork-bot+netdevbpf@kernel.org
To: Coco Li <lixiaoyan@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, willemb@google.com
Subject: Re: [PATCH net 1/2] udp: using datalen to cap ipv6 udp max gso segments
Date: Fri, 24 Dec 2021 03:30:12 +0000 [thread overview]
Message-ID: <164031661297.11818.12735840556675530099.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211223222441.2975883-1-lixiaoyan@google.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 23 Dec 2021 22:24:40 +0000 you wrote:
> The max number of UDP gso segments is intended to cap to
> UDP_MAX_SEGMENTS, this is checked in udp_send_skb().
>
> skb->len contains network and transport header len here, we should use
> only data len instead.
>
> This is the ipv6 counterpart to the below referenced commit,
> which missed the ipv6 change
>
> [...]
Here is the summary with links:
- [net,1/2] udp: using datalen to cap ipv6 udp max gso segments
https://git.kernel.org/netdev/net/c/736ef37fd9a4
- [net,2/2] selftests: Calculate udpgso segment count without header adjustment
https://git.kernel.org/netdev/net/c/5471d5226c3b
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-12-24 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 22:24 [PATCH net 1/2] udp: using datalen to cap ipv6 udp max gso segments Coco Li
2021-12-23 22:24 ` [PATCH net 2/2] selftests: Calculate udpgso segment count without header adjustment Coco Li
2021-12-24 3:19 ` [PATCH net 1/2] udp: using datalen to cap ipv6 udp max gso segments Jakub Kicinski
2021-12-24 3:22 ` Jakub Kicinski
2021-12-24 3:48 ` Willem de Bruijn
2021-12-24 3: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=164031661297.11818.12735840556675530099.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=lixiaoyan@google.com \
--cc=netdev@vger.kernel.org \
--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.