From: Thibaut Sautereau <thibaut.sautereau@clip-os.org>
To: dm-devel@redhat.com, Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: dm-crypt error when CONFIG_CRYPTO_AUTHENC is disabled
Date: Fri, 20 Sep 2019 17:44:34 +0200 [thread overview]
Message-ID: <20190920154434.GA923@gandi.net> (raw)
Hi,
I just got a dm-crypt "crypt: Error allocating crypto tfm" error when
trying to "cryptsetup open" a volume. I found out that it was only
happening when I disabled CONFIG_CRYPTO_AUTHENC.
drivers/md/dm-crypt.c includes the crypto/authenc.h header and seems to
use some CRYPTO_AUTHENC-related stuff. Therefore, shouldn't
CONFIG_DM_CRYPT select CONFIG_CRYPTO_AUTHENC?
--
Thibaut Sautereau
CLIP OS developer
next reply other threads:[~2019-09-20 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 15:44 Thibaut Sautereau [this message]
2019-09-20 17:37 ` dm-crypt error when CONFIG_CRYPTO_AUTHENC is disabled Mike Snitzer
2019-09-20 19:21 ` Milan Broz
2019-09-20 21:27 ` Mike Snitzer
2019-09-20 21:47 ` [dm-devel] " Eric Biggers
2019-09-23 8:20 ` Thibaut Sautereau
2019-09-23 9:46 ` Milan Broz
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=20190920154434.GA923@gandi.net \
--to=thibaut.sautereau@clip-os.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
/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).