From: Milan Broz <mbroz@redhat.com>
Cc: dm-crypt@saout.de
Subject: [dm-crypt] SLED10 broken dm-crypt module (was Re: [ANNOUNCE] cryptsetup 1.1.1-rc1 (test release candidate))
Date: Tue, 04 May 2010 17:17:13 +0200 [thread overview]
Message-ID: <4BE03A79.7060805@redhat.com> (raw)
In-Reply-To: <20100501180640.9035E6545B3@c-in3ws--03-02.sv2.lotusliveops.com>
On 05/01/2010 08:06 PM, Si St wrote:
> query_device: crypt_query_device API call
> [(equal) ,query_device:299] crypt_query_device(&co) == 0
> [(equal) ,query_device:302] crypt_query_device(&co) == 1
> [(success),query_device:304] strncmp(crypt_get_dir(), DMDIR, 11)
> [(success),query_device:305] strcmp(co.cipher, "aes-cbc-essiv:sha256")
> FAIL line 305 [query_device]: code 1,
> FAIL: api-test
For the archive:
this fail is because SLED10 (2.6.16.60-0.21-default kernel) contains broken dm-crypt module.
It seems this upstream patch is missing
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=37af6560f7978c60791b5f3df17ce8b3e97f2d6e
it causes device-mapper table status to incorrectly prints cipher this way:
0 65536 crypt cbc(aes)-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 7:0 0
The correct form is
0 65536 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 7:0 0
So cryptsetup cannot work properly with this kernel.
Milan
prev parent reply other threads:[~2010-05-04 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 18:06 [dm-crypt] [ANNOUNCE] cryptsetup 1.1.1-rc1 (test release candidate) Si St
2010-05-01 20:10 ` Milan Broz
2010-05-04 15:17 ` Milan Broz [this message]
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=4BE03A79.7060805@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
/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.