From: Milan Broz <mbroz@redhat.com>
To: "Uwe Kleine-König" <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>
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - RT patch set seem to break it
Date: Tue, 30 Oct 2012 10:55:17 +0100 [thread overview]
Message-ID: <508FA405.2050509@redhat.com> (raw)
In-Reply-To: <20121030094001.GV639@pengutronix.de>
On 10/30/2012 10:40 AM, Uwe Kleine-König 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
WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <mbroz@redhat.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Tvrtko Ursulin <tvrtko@ursulin.net>,
Milan Broz <gmazyland@gmail.com>,
dm-crypt@saout.de, linux-kernel@vger.kernel.org,
okozina@redhat.com, linux-rt-users@vger.kernel.org
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - RT patch set seem to break it
Date: Tue, 30 Oct 2012 10:55:17 +0100 [thread overview]
Message-ID: <508FA405.2050509@redhat.com> (raw)
In-Reply-To: <20121030094001.GV639@pengutronix.de>
On 10/30/2012 10:40 AM, Uwe Kleine-König 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
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <mbroz@redhat.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Tvrtko Ursulin <tvrtko@ursulin.net>,
Milan Broz <gmazyland@gmail.com>,
dm-crypt@saout.de, linux-kernel@vger.kernel.org,
okozina@redhat.com, linux-rt-users@vger.kernel.org
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - RT patch set seem to break it
Date: Tue, 30 Oct 2012 10:55:17 +0100 [thread overview]
Message-ID: <508FA405.2050509@redhat.com> (raw)
In-Reply-To: <20121030094001.GV639@pengutronix.de>
On 10/30/2012 10:40 AM, Uwe Kleine-König 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
next prev parent reply other threads:[~2012-10-30 9:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 20:44 [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4? Tvrtko Ursulin
2012-10-20 20:44 ` Tvrtko Ursulin
2012-10-21 9:53 ` [dm-crypt] " Milan Broz
2012-10-21 12:03 ` Tvrtko Ursulin
2012-10-21 12:20 ` Zdenek Kaspar
2012-10-21 12:36 ` Tvrtko Ursulin
2012-10-21 12:36 ` Tvrtko Ursulin
2012-10-21 19:29 ` [dm-crypt] " Milan Broz
2012-10-21 19:29 ` Milan Broz
2012-10-21 20:03 ` [dm-crypt] " Tvrtko Ursulin
2012-10-21 20:03 ` Tvrtko Ursulin
2012-10-22 14:27 ` [dm-crypt] " Ondrej Kozina
2012-10-29 19:31 ` Tvrtko Ursulin
2012-10-29 19:31 ` Tvrtko Ursulin
2012-10-29 19:47 ` [dm-crypt] " Milan Broz
2012-10-29 19:47 ` Milan Broz
2012-10-29 20:14 ` Tvrtko Ursulin
2012-10-29 20:14 ` Tvrtko Ursulin
2012-10-29 20:45 ` [dm-crypt] cryptsetup not working under 3.6 - RT patch set seem to break it Tvrtko Ursulin
2012-10-29 20:45 ` Tvrtko Ursulin
2012-10-29 20:45 ` Tvrtko Ursulin
2012-10-29 23:51 ` [dm-crypt] " Thomas Gleixner
2012-10-29 23:51 ` Thomas Gleixner
2012-10-30 9:40 ` Uwe Kleine-König
2012-10-30 9:40 ` Uwe Kleine-König
2012-10-30 9:55 ` Milan Broz [this message]
2012-10-30 9:55 ` Milan Broz
2012-10-30 9:55 ` Milan Broz
2012-10-30 15:27 ` [dm-crypt] [PATCH] Fix crypto api init for 3.6.4-rt10 Milan Broz
2012-10-30 15:27 ` Milan Broz
2012-10-30 17:57 ` [dm-crypt] " Thomas Gleixner
2012-10-30 17:57 ` Thomas Gleixner
2012-10-30 20:35 ` [dm-crypt] " Uwe Kleine-König
2012-10-30 20:35 ` Uwe Kleine-König
2012-10-30 20:35 ` Uwe Kleine-König
2012-10-30 18:24 ` [dm-crypt] " Tvrtko Ursulin
2012-10-30 18:24 ` Tvrtko Ursulin
2012-10-29 20:48 ` [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4? Milan Broz
2012-10-29 20:48 ` Milan Broz
2012-10-21 10:00 ` Heinz Diehl
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=508FA405.2050509@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=gmazyland@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=okozina@redhat.com \
--cc=tvrtko@ursulin.net \
--cc=u.kleine-koenig@pengutronix.de \
/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.