public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Vadim Fedorenko <vfedorenko@novek•ru>
Cc: dsahern@kernel•org, netdev@vger•kernel.org,
	roopa@cumulusnetworks•com, kuba@kernel•org,
	yoshfuji@linux-ipv6•org, davem@davemloft•net
Subject: Re: [PATCH net v2] net: lwtunnel: handle MTU calculation in forwading
Date: Mon, 28 Jun 2021 20:10:04 +0000	[thread overview]
Message-ID: <162491100403.2562.9093785941784611032.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210625162139.9067-1-vfedorenko@novek.ru>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Fri, 25 Jun 2021 19:21:39 +0300 you wrote:
> Commit 14972cbd34ff ("net: lwtunnel: Handle fragmentation") moved
> fragmentation logic away from lwtunnel by carry encap headroom and
> use it in output MTU calculation. But the forwarding part was not
> covered and created difference in MTU for output and forwarding and
> further to silent drops on ipv4 forwarding path. Fix it by taking
> into account lwtunnel encap headroom.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: lwtunnel: handle MTU calculation in forwading
    https://git.kernel.org/netdev/net/c/fade56410c22

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



      parent reply	other threads:[~2021-06-28 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 16:21 [PATCH net v2] net: lwtunnel: handle MTU calculation in forwading Vadim Fedorenko
2021-06-26 17:18 ` David Ahern
2021-06-26 21:41   ` Vadim Fedorenko
2021-06-28 18:45     ` David Ahern
2021-06-26 23:21   ` Vadim Fedorenko
2021-06-28 20:10 ` 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=162491100403.2562.9093785941784611032.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=dsahern@kernel$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=roopa@cumulusnetworks$(echo .)com \
    --cc=vfedorenko@novek$(echo .)ru \
    --cc=yoshfuji@linux-ipv6$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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