From: Eric Biggers <ebiggers@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-fscrypt@vger.kernel.org
Subject: [xfstests-bld PATCH] kernel-configs: enable CONFIG_CRYPTO_ESSIV in 5.4 configs
Date: Mon, 2 Dec 2019 15:23:40 -0800 [thread overview]
Message-ID: <20191202232340.243744-1-ebiggers@kernel.org> (raw)
From: Eric Biggers <ebiggers@google.com>
On kernel 5.5 and later, CONFIG_CRYPTO_ESSIV is needed for one of the
fscrypt tests (generic/549) to run.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
kernel-configs/i386-config-5.4 | 1 +
kernel-configs/x86_64-config-5.4 | 1 +
2 files changed, 2 insertions(+)
diff --git a/kernel-configs/i386-config-5.4 b/kernel-configs/i386-config-5.4
index 195211e..3495a0d 100644
--- a/kernel-configs/i386-config-5.4
+++ b/kernel-configs/i386-config-5.4
@@ -170,6 +170,7 @@ CONFIG_IMA_APPRAISE=y
CONFIG_EVM=y
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
CONFIG_CRYPTO_ADIANTUM=y
+CONFIG_CRYPTO_ESSIV=y
CONFIG_CRYPTO_CRC32C_INTEL=y
CONFIG_CRYPTO_CRC32_PCLMUL=y
CONFIG_CRYPTO_AES_NI_INTEL=y
diff --git a/kernel-configs/x86_64-config-5.4 b/kernel-configs/x86_64-config-5.4
index 9a6baaa..e8d2b68 100644
--- a/kernel-configs/x86_64-config-5.4
+++ b/kernel-configs/x86_64-config-5.4
@@ -177,6 +177,7 @@ CONFIG_IMA_APPRAISE=y
CONFIG_EVM=y
# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
CONFIG_CRYPTO_ADIANTUM=y
+CONFIG_CRYPTO_ESSIV=y
CONFIG_CRYPTO_CRC32C_INTEL=y
CONFIG_CRYPTO_CRC32_PCLMUL=y
CONFIG_CRYPTO_AES_NI_INTEL=y
--
2.24.0.393.g34dc348eaf-goog
next reply other threads:[~2019-12-02 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 23:23 Eric Biggers [this message]
2019-12-16 17:26 ` [xfstests-bld PATCH] kernel-configs: enable CONFIG_CRYPTO_ESSIV in 5.4 configs Eric Biggers
2019-12-16 23:06 ` Theodore Y. Ts'o
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=20191202232340.243744-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=tytso@mit.edu \
/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).