From: Milan Broz <gmazyland@gmail.com>
To: Johannes Ernst <johannes.ernst@gmail.com>
Cc: dm-crypt@saout.de,
Lars Winterfeld <lars.winterfeld@tu-ilmenau.de>,
linux-crypto@vger.kernel.org
Subject: Re: [dm-crypt] cryptsetup problem on Raspberry Pi 2 w 512bit key-size (works on Raspberry Pi 1, x86_64, 256bit)
Date: Mon, 23 Feb 2015 20:03:19 +0100 [thread overview]
Message-ID: <54EB7977.70503@gmail.com> (raw)
In-Reply-To: <707C4FCB-0182-44E3-946A-19434F32BEAB@gmail.com>
On 02/23/2015 07:44 PM, Johannes Ernst wrote:
> 1. There was a (cryptic, to me) comment by one of the core Arch Linux
> ARM developers on my post. He said "Something on my mind about kernel
> mode neon on imx6, can't find it now”
> (http://archlinuxarm.org/forum/viewtopic.php?f=60&t=8489&p=45395#p45364)
> I have little idea what this could mean, but I figure I pass it on in
> case somebody here does.
>
> 2. I disabled the mentioned kernel modules:
>
> blacklist af_alg blacklist algif_skcipher
>
> and, magic happens, it behaves as intended: cryptsetup opens file on
> first try.
Ok, so it means there is something wrong when using AF_ALG/SKCIPHER
on new Raspberry Pi2.
(Please can you post luksDump as well - just to be sure which mode
and cipher it is - I guess it is aes-xts but cannot find it in log.)
CC kernel crypto api list ... maybe someone knows about known problem here.
The link to failing cryptsetup debug log for reference:
http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/7973
Thanks,
Milan
next prev parent reply other threads:[~2015-02-23 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 21:37 [dm-crypt] cryptsetup problem on Raspberry Pi 2 w 512bit key-size (works on Raspberry Pi 1, x86_64, 256bit) Johannes Ernst
2015-02-20 22:25 ` Lars Winterfeld
2015-02-20 22:59 ` Johannes Ernst
2015-02-21 6:53 ` Milan Broz
2015-02-22 19:29 ` Johannes Ernst
2015-02-22 19:36 ` Johannes Ernst
2015-02-22 19:40 ` Johannes Ernst
2015-02-22 20:20 ` Milan Broz
2015-02-23 18:44 ` Johannes Ernst
2015-02-23 19:03 ` Milan Broz [this message]
2015-02-23 23:02 ` Johannes Ernst
2015-02-28 0:48 ` 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=54EB7977.70503@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=johannes.ernst@gmail.com \
--cc=lars.winterfeld@tu-ilmenau.de \
--cc=linux-crypto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox