[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220119000014.1745223-1-evitayan@google.com>
Date: Tue, 18 Jan 2022 16:00:12 -0800
From: Yan Yan <evitayan@...gle.com>
To: Steffen Klassert <steffen.klassert@...unet.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,
Yan Yan <evitayan@...gle.com>
Subject: [PATCH v2 0/2] Fix issues in xfrm_migrate
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
include/net/xfrm.h | 5 +++--
net/key/af_key.c | 2 +-
net/xfrm/xfrm_policy.c | 14 ++++++++------
net/xfrm/xfrm_state.c | 15 +++++++++++----
net/xfrm/xfrm_user.c | 6 +++++-
5 files changed, 28 insertions(+), 14 deletions(-)
base-commit: fe8152b38d3a994c4c6fdbc0cd6551d569a5715a
--
2.34.1.703.g22d0c6ccf7-goog
Powered by blists - more mailing lists