netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thomas Bartschies <thomas.bartschies@cvk.de>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [Patch] net: af_key: check encryption module availability consistency
Date: Tue, 17 May 2022 17:44:47 -0700	[thread overview]
Message-ID: <20220517174447.0e596e4f@kernel.org> (raw)
In-Reply-To: <20220516125730.4446D160219F3@cvk027.cvk.de>

On Mon, 16 May 2022 14:57:30 +0200 (CEST) Thomas Bartschies 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>

This has not made it into patchwork.

Did you put the list on BCC or something? If so how would people 
on the list see replies to this patch?

Please repost it with appropriate To: and CC: lists.
To: davem@davemloft.net
CC: everyone from scripts/get_maintainer

  reply	other threads:[~2022-05-18  0:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 12:57 [Patch] net: af_key: check encryption module availability consistency Thomas Bartschies
2022-05-18  0:44 ` Jakub Kicinski [this message]
2022-05-18  6:36   ` AW: " Bartschies, Thomas
  -- strict thread matches above, loose matches on Subject: below --
2022-05-18  6:32 Thomas Bartschies
2022-05-18  8:13 ` Steffen Klassert
2022-05-18 12:00 ` patchwork-bot+netdevbpf
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=20220517174447.0e596e4f@kernel.org \
    --to=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --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).