[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220127062048.GP1223722@gauss3.secunet.de>
Date: Thu, 27 Jan 2022 07:20:48 +0100
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Yan Yan <evitayan@...gle.com>
CC: <netdev@...r.kernel.org>, Herbert Xu <herbert@...dor.apana.org.au>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, <lorenzo@...gle.com>,
<maze@...gle.com>, <nharold@...gle.com>, <benedictwong@...gle.com>
Subject: Re: [PATCH v2 0/2] Fix issues in xfrm_migrate
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!
Powered by blists - more mailing lists