From: Eric Biggers <ebiggers@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto List <linux-crypto@vger.kernel.org>,
Alexander Potapenko <glider@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Robert Elliott <elliott@hpe.com>
Subject: Re: linux-next: manual merge of the mm tree with the crypto tree
Date: Tue, 6 Sep 2022 15:12:28 -0700 [thread overview]
Message-ID: <YxfFzGObDWsylCK+@quark> (raw)
In-Reply-To: <20220906202017.5093fd23@canb.auug.org.au>
On Tue, Sep 06, 2022 at 08:20:17PM +1000, Stephen Rothwell wrote:
> diff --git a/arch/x86/crypto/Kconfig b/arch/x86/crypto/Kconfig
> index 9bb0f7939c6b..856f5d8ca65f 100644
> --- a/arch/x86/crypto/Kconfig
> +++ b/arch/x86/crypto/Kconfig
> @@ -5,6 +5,7 @@ menu "Accelerated Cryptographic Algorithms for CPU (x86)"
> config CRYPTO_CURVE25519_X86
> tristate "Public key crypto: Curve25519 (ADX)"
> depends on X86 && 64BIT
> + depends on !KMSAN # avoid false positives from assembly
> select CRYPTO_LIB_CURVE25519_GENERIC
> select CRYPTO_ARCH_HAVE_LIB_CURVE25519
> help
> @@ -16,6 +17,7 @@ config CRYPTO_CURVE25519_X86
> config CRYPTO_AES_NI_INTEL
> tristate "Ciphers: AES, modes: ECB, CBC, CTS, CTR, XTR, XTS, GCM (AES-NI)"
> depends on X86
> + depends on !KMSAN # avoid false positives from assembly
> select CRYPTO_AEAD
> select CRYPTO_LIB_AES
> select CRYPTO_ALGAPI
> @@ -32,6 +34,7 @@ config CRYPTO_AES_NI_INTEL
> config CRYPTO_BLOWFISH_X86_64
> tristate "Ciphers: Blowfish, modes: ECB, CBC"
> depends on X86 && 64BIT
> + depends on !KMSAN # avoid false positives from assembly
> select CRYPTO_SKCIPHER
> select CRYPTO_BLOWFISH_COMMON
> imply CRYPTO_CTR
> @@ -44,6 +47,7 @@ config CRYPTO_BLOWFISH_X86_64
> config CRYPTO_CAMELLIA_X86_64
> tristate "Ciphers: Camellia with modes: ECB, CBC"
> depends on X86 && 64BIT
> + depends on !KMSAN # avoid false positives from assembly
> select CRYPTO_SKCIPHER
> imply CRYPTO_CTR
> help
> @@ -55,6 +59,7 @@ config CRYPTO_CAMELLIA_X86_64
> config CRYPTO_CAMELLIA_AESNI_AVX_X86_64
> tristate "Ciphers: Camellia with modes: ECB, CBC (AES-NI/AVX)"
> depends on X86 && 64BIT
> + depends on !KMSAN # avoid false positives from assembly
> select CRYPTO_SKCIPHER
> select CRYPTO_CAMELLIA_X86_64
> select CRYPTO_SIMD
Are there any options in arch/x86/crypto/Kconfig that *don't* need a dependency
on !KMSAN? If not, this could be done in a much simpler way.
- Eric
next prev parent reply other threads:[~2022-09-06 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 10:20 linux-next: manual merge of the mm tree with the crypto tree Stephen Rothwell
2022-09-06 22:12 ` Eric Biggers [this message]
2022-09-07 9:18 ` Alexander Potapenko
2022-09-07 20:41 ` Andrew Morton
2022-09-12 9:37 ` Alexander Potapenko
2022-09-12 18:59 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2022-07-18 9:53 Stephen Rothwell
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=YxfFzGObDWsylCK+@quark \
--to=ebiggers@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=elliott@hpe.com \
--cc=glider@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.