From: Milan Broz <mbroz@redhat.com>
To: Martin Hicks <mort@bork.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] luksFormat hangs
Date: Tue, 28 Jun 2011 22:14:37 +0200 [thread overview]
Message-ID: <4E0A362D.40503@redhat.com> (raw)
In-Reply-To: <BANLkTinQVZ8obgY34rx-7xUERY7hOS_QB1Mqj2zv=c88hMModw@mail.gmail.com>
Hi,
On 06/28/2011 09:56 PM, Martin Hicks wrote:
> I'm trying to create a luks device on an embedded platform running
> kernel 2.6.37 and cryptsetup 1.3.1. I'm sure I've done this before,
> but when I tried today I end up with a hang that consumes all CPU and
> based on a combination of --debug and strace I think it is in the
> PBKDF2_perforance_check function.
well, I would really like to know what went wrong there.
Is it something new in 1.3.1? (It shouldn't, there was no changes).
Which compile option are you using (configure options)?
(mainly which crypto backend - libgcrypt?)
Anything special with libc, environment or so?
> /conf/root # cryptsetup --debug -q luksFormat /dev/dtdb1
Can you try to add "-i 1" - is is still looping?
> The platform is ppc mpc8379-rdb. I've tried on the platform with the
> hardware encryption engine and on one without, although I don't think
> I'm getting to the stage where the kernel really cares about that.
If it is loops in PBKDF2 perf. check, I do not think the problem is in hw
acceleration (depends if userspace lib uses hw acceleration but I think
it is not, hw acceleration is used probably in kernel only.)
I guess "cryptsetup create" command work without problem, right?
Milan
next prev parent reply other threads:[~2011-06-28 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 19:56 [dm-crypt] luksFormat hangs Martin Hicks
2011-06-28 20:10 ` Arno Wagner
2011-06-28 20:14 ` Milan Broz [this message]
2011-06-28 20:23 ` Martin Hicks
2011-06-28 20:30 ` Milan Broz
2011-06-28 20:34 ` Martin Hicks
2011-06-30 17:53 ` Martin Hicks
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=4E0A362D.40503@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=mort@bork.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.