From: Yan Yan <evitayan@google.com>
To: Steffen Klassert <steffen.klassert@secunet.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, Yan Yan <evitayan@google.com>
Subject: [PATCH v2 0/2] Fix issues in xfrm_migrate
Date: Tue, 18 Jan 2022 16:00:12 -0800 [thread overview]
Message-ID: <20220119000014.1745223-1-evitayan@google.com> (raw)
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
next reply other threads:[~2022-01-19 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 0:00 Yan Yan [this message]
2022-01-19 0:00 ` [PATCH v2 1/2] xfrm: Check if_id in xfrm_migrate 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 ` [PATCH v2 0/2] Fix issues in xfrm_migrate Steffen Klassert
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=20220119000014.1745223-1-evitayan@google.com \
--to=evitayan@google.com \
--cc=benedictwong@google.com \
--cc=davem@davemloft.net \
--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 \
--cc=steffen.klassert@secunet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.