From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>,
<netdev@vger.kernel.org>
Subject: pull request (net-next): ipsec-next 2022-01-06
Date: Thu, 6 Jan 2022 10:13:43 +0100 [thread overview]
Message-ID: <20220106091350.3038869-1-steffen.klassert@secunet.com> (raw)
1) Fix some clang_analyzer warnings about never read variables.
From luo penghao.
2) Check for pols[0] only once in xfrm_expand_policies().
From Jean Sacren.
3) The SA curlft.use_time was updated only on SA cration time.
Update whenever the SA is used. From Antony Antony
4) Add support for SM3 secure hash.
From Xu Jia.
5) Add support for SM4 symmetric cipher algorithm.
From Xu Jia.
6) Add a rate limit for SA mapping change messages.
From Antony Antony.
Please pull or let me know if there are problems.
Thanks!
The following changes since commit bb8cecf8ba127abca8ccd102207a59c55fdae515:
Merge branch 'lan78xx-napi' (2021-11-18 12:11:51 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
for you to fetch changes up to 4e484b3e969b52effd95c17f7a86f39208b2ccf4:
xfrm: rate limit SA mapping change message to user space (2021-12-23 09:32:51 +0100)
----------------------------------------------------------------
Antony Antony (2):
xfrm: update SA curlft.use_time
xfrm: rate limit SA mapping change message to user space
Jean Sacren (1):
net: xfrm: drop check of pols[0] for the second time
Xu Jia (2):
xfrm: Add support for SM3 secure hash
xfrm: Add support for SM4 symmetric cipher algorithm
luo penghao (2):
ipv6/esp6: Remove structure variables and alignment statements
xfrm: Remove duplicate assignment
include/net/xfrm.h | 5 +++++
include/uapi/linux/pfkeyv2.h | 2 ++
include/uapi/linux/xfrm.h | 1 +
net/ipv6/esp6.c | 3 +--
net/xfrm/xfrm_algo.c | 41 +++++++++++++++++++++++++++++++++++++++++
net/xfrm/xfrm_compat.c | 6 ++++--
net/xfrm/xfrm_input.c | 1 +
net/xfrm/xfrm_output.c | 1 +
net/xfrm/xfrm_policy.c | 3 +--
net/xfrm/xfrm_state.c | 23 ++++++++++++++++++++++-
net/xfrm/xfrm_user.c | 18 +++++++++++++++++-
11 files changed, 96 insertions(+), 8 deletions(-)
next reply other threads:[~2022-01-06 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 9:13 Steffen Klassert [this message]
2022-01-06 9:13 ` [PATCH 1/7] ipv6/esp6: Remove structure variables and alignment statements Steffen Klassert
2022-01-06 12:20 ` patchwork-bot+netdevbpf
2022-01-06 9:13 ` [PATCH 2/7] xfrm: Remove duplicate assignment Steffen Klassert
2022-01-06 9:13 ` [PATCH 3/7] net: xfrm: drop check of pols[0] for the second time Steffen Klassert
2022-01-06 9:13 ` [PATCH 4/7] xfrm: update SA curlft.use_time Steffen Klassert
2022-01-06 9:13 ` [PATCH 5/7] xfrm: Add support for SM3 secure hash Steffen Klassert
2022-01-06 9:13 ` [PATCH 6/7] xfrm: Add support for SM4 symmetric cipher algorithm Steffen Klassert
2022-01-06 9:13 ` [PATCH 7/7] xfrm: rate limit SA mapping change message to user space Steffen Klassert
2022-01-06 12:20 ` pull request (net-next): ipsec-next 2022-01-06 patchwork-bot+netdevbpf
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=20220106091350.3038869-1-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).