mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Lina Wang <lina.wang@mediatek.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	"David Ahern" <dsahern@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] xfrm: fix tunnel model fragmentation behavior
Date: Wed, 23 Feb 2022 09:25:10 +0100	[thread overview]
Message-ID: <20220223082510.GL17351@gauss3.secunet.de> (raw)
In-Reply-To: <20220222021803.27965-1-lina.wang@mediatek.com>

On Tue, Feb 22, 2022 at 10:18:04AM +0800, Lina Wang wrote:
> On Mon, 2022-02-21 at 12:04 +0100, Steffen Klassert wrote:
> > On Mon, Feb 21, 2022 at 01:16:48PM +0800, Lina Wang wrote:
> > > in tunnel mode, if outer interface(ipv4) is less, it is easily to
> We have two commits in the ipsec tree that address a very similar
> > issue. That is:
> > 
> > commit 6596a0229541270fb8d38d989f91b78838e5e9da
> > xfrm: fix MTU regression
> > 
> > and
> > 
> > commit a6d95c5a628a09be129f25d5663a7e9db8261f51
> > Revert "xfrm: xfrm_state_mtu should return at least 1280 for ipv6"
> > 
> > Can you please doublecheck that the issue you are fixing still
> > exist in the ipsec tree?
> 
> Yes, I know the two patches, which didnot help for my scenary. Whatever 
> commit a6d95c5a62 exist or not, there still is double fragment issue. From
> commit 6596a022's mail thread, owner has met double fragment issue, I am 
> not sure if it is the same with mine.

Thanks for the doublecking this!

  reply	other threads:[~2022-02-23  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21  5:16 Lina Wang
2022-02-21 11:04 ` Steffen Klassert
2022-02-22  2:18   ` Lina Wang
2022-02-23  8:25     ` Steffen Klassert [this message]
2022-02-23  8:31 ` Steffen Klassert
2022-02-24  6:15   ` Lina Wang

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=20220223082510.GL17351@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=lina.wang@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --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
all inboxes | Powered by JetHome®