DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko@ursulin.net>
To: Zdenek Kaspar <zkaspar82@gmail.com>
Cc: dm-crypt@saout.de, Milan Broz <gmazyland@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4?
Date: Sun, 21 Oct 2012 13:36:49 +0100	[thread overview]
Message-ID: <5083EC61.8070505@ursulin.net> (raw)
In-Reply-To: <5083E87B.2080908@gmail.com>

On 21/10/12 13:20, Zdenek Kaspar wrote:
>>> 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?
>>
>> I both working 3.4 and non-working 3.6 situation is the same:
>>
>> CONFIG_CRYPTO_CBC=y
>> CONFIG_CRYPTO_SHA256=m
>
> Compare please:
> grep CONFIG_CRYPTO /boot/config-3.4
> grep CONFIG_CRYPTO /boot/config-3.6
>
> One of the problem could be that your configuration misses something
> like: CONFIG_CRYPTO_BLKCIPHER, CONFIG_CRYPTO_MANAGER, etc.. or some of
> those could changed into modules and are not getting loaded..

Here it is:

--- 3.4	2012-10-21 13:32:27.289602863 +0100
+++ 3.6	2012-10-21 13:32:23.824602841 +0100
@@ -1,3 +1,4 @@
+CONFIG_CRYPTO_ABLK_HELPER_X86=m
  CONFIG_CRYPTO_AEAD2=y
  CONFIG_CRYPTO_AEAD=m
  CONFIG_CRYPTO_AES=m
@@ -27,15 +28,14 @@
  CONFIG_CRYPTO_CTS=m
  CONFIG_CRYPTO_DEFLATE=m
  CONFIG_CRYPTO_DES=m
-CONFIG_CRYPTO_DEV_PADLOCK_AES=m
-CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
-CONFIG_CRYPTO_DEV_PADLOCK=y
+# CONFIG_CRYPTO_DEV_PADLOCK is not set
  CONFIG_CRYPTO_ECB=y
  CONFIG_CRYPTO_FCRYPT=m
  CONFIG_CRYPTO_GCM=m
  CONFIG_CRYPTO_GF128MUL=m
  CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m
  CONFIG_CRYPTO_GHASH=m
+CONFIG_CRYPTO_GLUE_HELPER_X86=m
  CONFIG_CRYPTO_HASH2=y
  CONFIG_CRYPTO_HASH=y
  CONFIG_CRYPTO_HMAC=y
@@ -64,6 +64,7 @@
  CONFIG_CRYPTO_SALSA20_X86_64=m
  CONFIG_CRYPTO_SEED=m
  CONFIG_CRYPTO_SEQIV=m
+CONFIG_CRYPTO_SERPENT_AVX_X86_64=m
  CONFIG_CRYPTO_SERPENT=m
  CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m
  CONFIG_CRYPTO_SHA1=m
@@ -73,6 +74,7 @@
  CONFIG_CRYPTO_TEA=m
  # CONFIG_CRYPTO_TEST is not set
  CONFIG_CRYPTO_TGR192=m
+CONFIG_CRYPTO_TWOFISH_AVX_X86_64=m
  CONFIG_CRYPTO_TWOFISH_COMMON=m
  CONFIG_CRYPTO_TWOFISH=m
  CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=m

Tvrtko

  reply	other threads:[~2012-10-21 12:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20 20:44 [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4? Tvrtko Ursulin
2012-10-21  9:53 ` Milan Broz
2012-10-21 12:03   ` Tvrtko Ursulin
2012-10-21 12:20     ` Zdenek Kaspar
2012-10-21 12:36       ` Tvrtko Ursulin [this message]
2012-10-21 19:29         ` Milan Broz
2012-10-21 20:03           ` Tvrtko Ursulin
2012-10-22 14:27             ` Ondrej Kozina
2012-10-29 19:31             ` Tvrtko Ursulin
2012-10-29 19:47               ` 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                         ` [dm-crypt] [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
2012-10-21 10:00 ` Heinz Diehl

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=5083EC61.8070505@ursulin.net \
    --to=tvrtko@ursulin.net \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zkaspar82@gmail.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