Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Magali Lemes <magali.lemes@canonical.com>
Cc: davem@davemloft.net, dsahern@gmail.com, edumazet@google.com,
	keescook@chromium.org, kuba@kernel.org, pabeni@redhat.com,
	shuah@kernel.org, tianjia.zhang@linux.alibaba.com,
	vfedorenko@novek.ru, andrei.gherzan@canonical.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4 0/4] Check if FIPS mode is enabled when running selftests
Date: Fri, 16 Jun 2023 05:30:22 +0000	[thread overview]
Message-ID: <168689342279.5522.4120374614331476094.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230613123222.631897-1-magali.lemes@canonical.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 13 Jun 2023 09:32:18 -0300 you wrote:
> Some test cases from net/tls, net/fcnal-test and net/vrf-xfrm-tests
> that rely on cryptographic functions to work and use non-compliant FIPS
> algorithms fail in FIPS mode.
> 
> In order to allow these tests to pass in a wider set of kernels,
>  - for net/tls, skip the test variants that use the ChaCha20-Poly1305
> and SM4 algorithms, when FIPS mode is enabled;
>  - for net/fcnal-test, skip the MD5 tests, when FIPS mode is enabled;
>  - for net/vrf-xfrm-tests, replace the algorithms that are not
> FIPS-compliant with compliant ones.
> 
> [...]

Here is the summary with links:
  - [v4,1/4] selftests/harness: allow tests to be skipped during setup
    https://git.kernel.org/netdev/net/c/372b304c1e51
  - [v4,2/4] selftests: net: tls: check if FIPS mode is enabled
    https://git.kernel.org/netdev/net/c/d113c395c67b
  - [v4,3/4] selftests: net: vrf-xfrm-tests: change authentication and encryption algos
    https://git.kernel.org/netdev/net/c/cb43c60e64ca
  - [v4,4/4] selftests: net: fcnal-test: check if FIPS mode is enabled
    https://git.kernel.org/netdev/net/c/d7a2fc1437f7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-06-16  5:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 12:32 [PATCH v4 0/4] Check if FIPS mode is enabled when running selftests Magali Lemes
2023-06-13 12:32 ` [PATCH v4 1/4] selftests/harness: allow tests to be skipped during setup Magali Lemes
2023-06-13 12:32 ` [PATCH v4 2/4] selftests: net: tls: check if FIPS mode is enabled Magali Lemes
2023-06-13 12:32 ` [PATCH v4 3/4] selftests: net: vrf-xfrm-tests: change authentication and encryption algos Magali Lemes
2023-06-13 12:32 ` [PATCH v4 4/4] selftests: net: fcnal-test: check if FIPS mode is enabled Magali Lemes
2023-06-16 19:33   ` [PATCH v4 4/4] selftests: net: fcnal-test: check if FIPS mode is enabled: manual merge Matthieu Baerts
2023-06-16 20:16     ` Matthieu Baerts
2023-06-16  5:30 ` patchwork-bot+netdevbpf [this message]

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=168689342279.5522.4120374614331476094.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrei.gherzan@canonical.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=magali.lemes@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=tianjia.zhang@linux.alibaba.com \
    --cc=vfedorenko@novek.ru \
    /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