From: Steffen Klassert <steffen.klassert@secunet.com>
To: Yan Yan <evitayan@google.com>
Cc: <netdev@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <lorenzo@google.com>,
<maze@google.com>, <nharold@google.com>,
<benedictwong@google.com>
Subject: Re: [PATCH v2 0/2] Fix issues in xfrm_migrate
Date: Thu, 27 Jan 2022 07:20:48 +0100 [thread overview]
Message-ID: <20220127062048.GP1223722@gauss3.secunet.de> (raw)
In-Reply-To: <20220119000014.1745223-1-evitayan@google.com>
On Tue, Jan 18, 2022 at 04:00:12PM -0800, Yan Yan wrote:
> This patch series include two patches to fix two issues in xfrm_migrate.
>
> PATCH 1/2 enables distinguishing SAs and SPs based on if_id during the
> xfrm_migrate flow. It fixes the problem that when there are multiple
> existing SPs with the same direction, the same xfrm_selector and
> different endpoint addresses, xfrm_migrate might fail.
>
> PATCH 2/2 enables xfrm_migrate to handle address family change by
> breaking the original xfrm_state_clone method into two steps so as to
> update the props.family before running xfrm_init_state.
>
> V1 -> V2:
> - Move xfrm_init_state() out of xfrm_state_clone()
> and called it after updating the address family
>
> Yan Yan (2):
> xfrm: Check if_id in xfrm_migrate
> xfrm: Fix xfrm migrate issues when address family changes
Applied, thanks a lot Yan!
prev parent reply other threads:[~2022-01-27 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 0:00 [PATCH v2 0/2] Fix issues in xfrm_migrate Yan Yan
2022-01-19 0:00 ` [PATCH v2 1/2] xfrm: Check if_id " Yan Yan
2022-01-19 0:00 ` [PATCH v2 2/2] xfrm: Fix xfrm migrate issues when address family changes Yan Yan
2022-01-27 6:20 ` Steffen Klassert [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=20220127062048.GP1223722@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=benedictwong@google.com \
--cc=davem@davemloft.net \
--cc=evitayan@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=nharold@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 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).