From: patchwork-bot+netdevbpf@kernel.org
To: Thomas Bartschies <thomas.bartschies@cvk.de>
Cc: davem@davemloft.net, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch] net: af_key: check encryption module availability consistency
Date: Wed, 18 May 2022 12:00:14 +0000 [thread overview]
Message-ID: <165287521444.18230.8052917231672464360.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220518063218.5336B160CF38F@cvk027.cvk.de>
Hello:
This patch was applied to netdev/net.git (master)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Wed, 18 May 2022 08:32:18 +0200 (CEST) you wrote:
> Since the recent introduction supporting the SM3 and SM4 hash algos for IPsec, the kernel
> produces invalid pfkey acquire messages, when these encryption modules are disabled. This
> happens because the availability of the algos wasn't checked in all necessary functions.
> This patch adds these checks.
>
> Signed-off-by: Thomas Bartschies <thomas.bartschies@cvk.de>
Here is the summary with links:
- net: af_key: check encryption module availability consistency
https://git.kernel.org/netdev/net/c/015c44d7bff3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-05-18 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 6:32 [Patch] net: af_key: check encryption module availability consistency Thomas Bartschies
2022-05-18 8:13 ` Steffen Klassert
2022-05-18 12:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-16 12:57 Thomas Bartschies
2022-05-18 0:44 ` Jakub Kicinski
2022-05-16 12:38 Thomas Bartschies
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=165287521444.18230.8052917231672464360.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=thomas.bartschies@cvk.de \
/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).