From: Michael Heyse <mhk@designassembly.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: which one is broken: VIA padlock aes or aes_i586?
Date: Wed, 22 Feb 2006 13:05:39 +0100 [thread overview]
Message-ID: <43FC5393.3080702@designassembly.de> (raw)
In-Reply-To: <20060222114531.GA4170@gondor.apana.org.au>
Herbert Xu wrote:
> On Wed, Feb 22, 2006 at 12:31:37PM +1100, herbert wrote:
>
>>I don't think this patch is your problem since it's part of the multiblock
>>code which doesn't exist in 2.6.12 at all. Of course the multiblock code
>>itself could be buggy. I'll take a look.
>
>
> OK I can't reproduce this. Please send me your dmcrypt setup line so
> I can try it here.
I'm using the cryptsetup tool (from http://www.saout.de/misc/dm-crypt/):
echo $KEY | cryptsetup -c aes-cbc-essiv:sha256 -h plain -s 256 create data /dev/vg0/data
$KEY contains 32 bytes of binary data. Do you need any other information? Here's all I can think of:
- parition /dev/vg0/data lies on a lvm2 volume group
- this volume group lies on a 4-disk software-raid 5 array
- size of the partition is 300 GB
- padlock aes works on kernel 2.6.15.4 but not on 2.6.16-rc1
- aes_i586 works on all kernels
Thanks,
Michael
next prev parent reply other threads:[~2006-02-22 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 12:27 which one is broken: VIA padlock aes or aes_i586? Michael Heyse
2006-02-22 1:31 ` Herbert Xu
2006-02-22 11:45 ` Herbert Xu
2006-02-22 12:05 ` Michael Heyse [this message]
2006-02-22 12:32 ` [SOLVED] " Michael Heyse
2006-02-22 12:43 ` Herbert Xu
2006-02-22 11:49 ` Michael Heyse
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=43FC5393.3080702@designassembly.de \
--to=mhk@designassembly.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
/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.