From: Steffen Klassert <steffen.klassert@secunet.com>
To: Jiri Bohac <jbohac@suse.cz>
Cc: Sabrina Dubroca <sd@queasysnail.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Mike Maloney" <maloneykernel@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] xfrm: fix MTU regression
Date: Wed, 26 Jan 2022 07:42:14 +0100 [thread overview]
Message-ID: <20220126064214.GO1223722@gauss3.secunet.de> (raw)
In-Reply-To: <20220125094102.ju7bhuplcxnkyv4x@dwarf.suse.cz>
On Tue, Jan 25, 2022 at 10:41:02AM +0100, Jiri Bohac wrote:
> On Mon, Jan 24, 2022 at 04:45:31PM +0100, Steffen Klassert wrote:
> > > sure; I'll send a v2 with added Fixes: for the original
> > > regression (749439bf), which will reappear once b515d263 (which
> > > causes the current regression) is reverted. Note this patch needs
> > > to be accompanied by the revert!
> > >
> > > > Btw. this fixes a xfrm issue, but touches only generic IPv6 code.
> > > > To which tree should this patch be applied? I can take it to
> > > > the ipsec tee, but would also be ok if it is applied directly
> > > > to the net tree.
> > >
> > > b515d263 touches xfrm code; but being a regression maybe we want
> > > the fastest track possible?
> >
> > The patch is already marked as 'awaiting upstream' in patchwork,
> > so I'll take it into the ipsec tree.
>
> OK, thanks! Will you also revert b515d263 in the ipsec tree?
You need to send a patch if you want to have this reverted.
next prev parent reply other threads:[~2022-01-26 6:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 17:31 xfrm regression: TCP MSS calculation broken by commit b515d263, results in TCP stall Jiri Bohac
2022-01-14 17:40 ` [PATCH] xfrm: fix MTU regression Jiri Bohac
2022-01-19 7:35 ` Steffen Klassert
2022-01-19 9:12 ` Jiri Bohac
2022-01-19 9:22 ` [PATCH v2] " Jiri Bohac
2022-01-26 6:41 ` Steffen Klassert
2022-01-24 15:45 ` [PATCH] " Steffen Klassert
2022-01-25 9:41 ` Jiri Bohac
2022-01-26 6:42 ` Steffen Klassert [this message]
2022-01-26 15:00 ` [PATCH] Revert "xfrm: xfrm_state_mtu should return at least 1280 for ipv6" Jiri Bohac
2022-02-01 6:46 ` Steffen Klassert
2022-02-15 14:59 ` Thorsten Leemhuis
2022-02-16 11:02 ` Steffen Klassert
2022-01-16 10:18 ` xfrm regression: TCP MSS calculation broken by commit b515d263, results in TCP stall Thorsten Leemhuis
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=20220126064214.GO1223722@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jbohac@suse.cz \
--cc=maloneykernel@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).