From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com
 [IPv6:2a00:1450:400c:c00::22f])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Mon, 23 Feb 2015 20:03:24 +0100 (CET)
Received: by wghb13 with SMTP id b13so696873wgh.0
 for <dm-crypt@saout.de>; Mon, 23 Feb 2015 11:03:23 -0800 (PST)
Message-ID: <54EB7977.70503@gmail.com>
Date: Mon, 23 Feb 2015 20:03:19 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <2E68FEAA-A69B-4E25-84F9-F30B2E7DFB69@gmail.com>
 <54E7B46D.8060805@tu-ilmenau.de>
 <E401AE9C-F988-4839-AC13-62D4FADD7290@gmail.com> <54E82B80.8000607@gmail.com>
 <EE112BA4-BDD8-4CB3-BD7B-BDA984D15089@gmail.com> <54EA39FA.7010408@gmail.com>
 <707C4FCB-0182-44E3-946A-19434F32BEAB@gmail.com>
In-Reply-To: <707C4FCB-0182-44E3-946A-19434F32BEAB@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [dm-crypt] cryptsetup problem on Raspberry Pi 2 w 512bit
 key-size (works on Raspberry Pi 1, x86_64, 256bit)
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Johannes Ernst <johannes.ernst@gmail.com>
Cc: dm-crypt@saout.de, Lars Winterfeld <lars.winterfeld@tu-ilmenau.de>, linux-crypto@vger.kernel.org

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