From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Benc <jbenc@redhat.com>
Cc: netdev@vger.kernel.org, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, kuba@kernel.org, pabeni@redhat.com,
eyal.birger@gmail.com
Subject: Re: [PATCH net v2] vxlan: calculate correct header length for GPE
Date: Mon, 24 Jul 2023 08:40:27 +0000 [thread overview]
Message-ID: <169018802751.2769.17292878954186029325.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <544e8c6d0f48af2be49809877c05c0445c0b0c0b.1689843872.git.jbenc@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 20 Jul 2023 11:05:56 +0200 you wrote:
> VXLAN-GPE does not add an extra inner Ethernet header. Take that into
> account when calculating header length.
>
> This causes problems in skb_tunnel_check_pmtu, where incorrect PMTU is
> cached.
>
> In the collect_md mode (which is the only mode that VXLAN-GPE
> supports), there's no magic auto-setting of the tunnel interface MTU.
> It can't be, since the destination and thus the underlying interface
> may be different for each packet.
>
> [...]
Here is the summary with links:
- [net,v2] vxlan: calculate correct header length for GPE
https://git.kernel.org/netdev/net/c/94d166c5318c
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:[~2023-07-24 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 9:05 [PATCH net v2] vxlan: calculate correct header length for GPE Jiri Benc
2023-07-21 12:46 ` Simon Horman
2023-07-24 8:40 ` 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=169018802751.2769.17292878954186029325.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=eyal.birger@gmail.com \
--cc=jbenc@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).