From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Mkq7tGJZbJP4 for <dm-crypt@saout.de>;
 Tue, 30 Oct 2012 10:55:50 +0100 (CET)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Tue, 30 Oct 2012 10:55:49 +0100 (CET)
Message-ID: <508FA405.2050509@redhat.com>
Date: Tue, 30 Oct 2012 10:55:17 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <5083C61C.5090807@gmail.com> <5083E4A8.3060501@ursulin.net>
 <5083E87B.2080908@gmail.com> <5083EC61.8070505@ursulin.net>
 <50844D01.9090805@gmail.com> <5084551E.5040304@ursulin.net>
 <508ED985.5060301@ursulin.net> <508EDD6E.7030908@gmail.com>
 <508EE395.9010709@ursulin.net> <508EEAF2.4090506@ursulin.net>
 <20121030094001.GV639@pengutronix.de>
In-Reply-To: <20121030094001.GV639@pengutronix.de>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - RT patch set seem
 to break it
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: =?ISO-8859-1?Q?Uwe_Kleine-K=F6nig?= <u.kleine-koenig@pengutronix.de>
Cc: Tvrtko Ursulin <tvrtko@ursulin.net>, linux-rt-users@vger.kernel.org, dm-crypt@saout.de, linux-kernel@vger.kernel.org, okozina@redhat.com, Milan Broz <gmazyland@gmail.com>

On 10/30/2012 10:40 AM, Uwe Kleine-K=F6nig wrote:
>> Ha, this is exciting, vanilla 3.6.4 works, with -rt10 patch it does not.
> I experienced that problem, too. This is on a laptop with encrypted
> rootfs, so debugging is a bit harder here. I am just setting up another
> machine to debug that.

FYI the problematic patch is peterz-srcu-crypto-chain.patch in rt10
patchset, after that, crypto_alloc_ablkcipher() now returns -ENOENT (-2)
in dmcrypt.

(I will check it later but maybe someone already playing with it...)

Milan