From: Milan Broz <gmazyland@gmail.com>
To: Tvrtko Ursulin <tvrtko@ursulin.net>
Cc: dm-crypt@saout.de, linux-kernel@vger.kernel.org
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4?
Date: Sun, 21 Oct 2012 11:53:32 +0200 [thread overview]
Message-ID: <5083C61C.5090807@gmail.com> (raw)
In-Reply-To: <50830D33.5050807@ursulin.net>
On 10/20/2012 10:44 PM, Tvrtko Ursulin wrote:
> But I repeat, even if I load the required modules before hand things do
> not work.
I would say you are still missing some modules.
> Kernel says this:
> device-mapper: table: 252:1: crypt: Error allocating crypto tfm
> device-mapper: ioctl: error adding target to table
It complains about aes-cbc-essiv:sha256.
It can be missing CBC od SHA256, but according the message I bet
you have no "cbc" block cipher mode module compiled.
Can you grep your final .config for CONFIG_CRYPTO_CBC and
CONFIG_CRYPTO_SHA256 a paste it here?
Milan
next prev parent reply other threads:[~2012-10-21 9:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 20:44 cryptsetup not working under 3.6 - regression from 3.4? Tvrtko Ursulin
2012-10-21 9:53 ` Milan Broz [this message]
2012-10-21 12:03 ` [dm-crypt] " Tvrtko Ursulin
[not found] ` <5083E87B.2080908@gmail.com>
2012-10-21 12:36 ` Tvrtko Ursulin
2012-10-21 19:29 ` Milan Broz
2012-10-21 20:03 ` Tvrtko Ursulin
2012-10-29 19:31 ` Tvrtko Ursulin
2012-10-29 19:47 ` [dm-crypt] " Milan Broz
2012-10-29 20:14 ` Tvrtko Ursulin
2012-10-29 20:45 ` [dm-crypt] cryptsetup not working under 3.6 - RT patch set seem to break it Tvrtko Ursulin
2012-10-29 23:51 ` Thomas Gleixner
2012-10-30 9:40 ` Uwe Kleine-König
2012-10-30 9:55 ` Milan Broz
2012-10-30 15:27 ` [PATCH] Fix crypto api init for 3.6.4-rt10 Milan Broz
2012-10-30 17:57 ` Thomas Gleixner
2012-10-30 20:35 ` Uwe Kleine-König
2012-10-30 18:24 ` Tvrtko Ursulin
2012-10-29 20:48 ` [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4? 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=5083C61C.5090807@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko@ursulin.net \
/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).