From: Yan Yan <evitayan@google•com>
To: steffen.klassert@secunet•com
Cc: herbert@gondor•apana.org.au, davem@davemloft•net,
netdev@vger•kernel.org, nharold@google•com,
benedictwong@google•com, maze@google•com, lorenzo@google•com,
Yan Yan <evitayan@google•com>
Subject: [PATCH v1 0/2] Fix issues in xfrm_migrate
Date: Wed, 22 Dec 2021 16:45:53 -0800 [thread overview]
Message-ID: <20211223004555.1284666-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.
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/xfrm/xfrm_policy.c | 14 ++++++++------
net/xfrm/xfrm_state.c | 38 +++++++++++++++++++++++++++-----------
net/xfrm/xfrm_user.c | 6 +++++-
4 files changed, 43 insertions(+), 20 deletions(-)
--
2.34.1.307.g9b7440fafd-goog
next reply other threads:[~2021-12-23 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 0:45 Yan Yan [this message]
2021-12-23 0:45 ` [PATCH v1 1/2] xfrm: Check if_id in xfrm_migrate Yan Yan
2021-12-25 18:30 ` kernel test robot
2021-12-23 0:45 ` [PATCH v1 2/2] xfrm: Fix xfrm migrate issues when address family changes Yan Yan
2021-12-26 2:18 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2022-01-06 0:52 [PATCH v1 0/2] Fix issues in xfrm_migrate Yan Yan
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=20211223004555.1284666-1-evitayan@google.com \
--to=evitayan@google$(echo .)com \
--cc=benedictwong@google$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=lorenzo@google$(echo .)com \
--cc=maze@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nharold@google$(echo .)com \
--cc=steffen.klassert@secunet$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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