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: [PATCH 0/2] pull request (net): ipsec 2023-03-15
Date: Wed, 15 Mar 2023 11:56:21 +0100 [thread overview]
Message-ID: <20230315105623.1396491-1-steffen.klassert@secunet.com> (raw)
1) Fix an information leak when dumping algos and encap.
From Herbert Xu
2) Allow transport-mode states with AF_UNSPEC selector
to allow for nested transport-mode states.
From Herbert Xu.
Please pull or let me know if there are problems.
Thanks!
The following changes since commit 2038cc592811209de20c4e094ca08bfb1e6fbc6c:
bnxt_en: Fix mqprio and XDP ring checking logic (2023-02-13 09:57:59 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git tags/ipsec-2023-03-15
for you to fetch changes up to c276a706ea1f51cf9723ed8484feceaf961b8f89:
xfrm: Allow transport-mode states with AF_UNSPEC selector (2023-02-24 10:07:24 +0100)
----------------------------------------------------------------
ipsec-2023-03-15
----------------------------------------------------------------
Herbert Xu (2):
xfrm: Zero padding when dumping algos and encap
xfrm: Allow transport-mode states with AF_UNSPEC selector
net/xfrm/xfrm_state.c | 5 -----
net/xfrm/xfrm_user.c | 45 +++++++++++++++++++++++++++++++++++++++++----
2 files changed, 41 insertions(+), 9 deletions(-)
next reply other threads:[~2023-03-15 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 10:56 Steffen Klassert [this message]
2023-03-15 10:56 ` [PATCH 1/2] xfrm: Zero padding when dumping algos and encap Steffen Klassert
2023-03-17 0:30 ` patchwork-bot+netdevbpf
2023-03-15 10:56 ` [PATCH 2/2] xfrm: Allow transport-mode states with AF_UNSPEC selector 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=20230315105623.1396491-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 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.