From: Milan Broz <gmazyland@gmail.com>
To: Tvrtko Ursulin <tvrtko@ursulin.net>
Cc: dm-crypt@saout.de, linux-kernel@vger.kernel.org, okozina@redhat.com
Subject: Re: [dm-crypt] cryptsetup not working under 3.6 - regression from 3.4?
Date: Mon, 29 Oct 2012 21:48:12 +0100 [thread overview]
Message-ID: <508EEB8C.8@gmail.com> (raw)
In-Reply-To: <508EE395.9010709@ursulin.net>
On 10/29/2012 09:14 PM, Tvrtko Ursulin wrote:
> Unless RT patchset is the culprit. Hm.. that would be unexpected, but I
> guess it is worth a shot. I'll let you know what happens without -rt.
Yes, try not patched mainline first.
Focus on the crypto api - if the crypto modules are not loading automatically, as you
said in previous mails, something is misconfigured there - it can be even
related to userspace tools (modprobe, udev, ...) check that you have recent versions.
It works for me here after "make oldconfig" with the .config you sent...
Milan
prev parent reply other threads:[~2012-10-29 20:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 20:44 cryptsetup not working under 3.6 - regression from 3.4? Tvrtko Ursulin
2012-10-21 9:53 ` [dm-crypt] " Milan Broz
2012-10-21 12:03 ` Tvrtko Ursulin
[not found] ` <5083E87B.2080908@gmail.com>
2012-10-21 12:36 ` Tvrtko Ursulin
2012-10-21 19:29 ` Milan Broz
2012-10-21 20:03 ` Tvrtko Ursulin
2012-10-29 19:31 ` Tvrtko Ursulin
2012-10-29 19:47 ` [dm-crypt] " Milan Broz
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 23:51 ` Thomas Gleixner
2012-10-30 9:40 ` Uwe Kleine-König
2012-10-30 9:55 ` Milan Broz
2012-10-30 15:27 ` [PATCH] Fix crypto api init for 3.6.4-rt10 Milan Broz
2012-10-30 17:57 ` Thomas Gleixner
2012-10-30 20:35 ` Uwe Kleine-König
2012-10-30 18:24 ` Tvrtko Ursulin
2012-10-29 20:48 ` Milan Broz [this message]
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=508EEB8C.8@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=okozina@redhat.com \
--cc=tvrtko@ursulin.net \
/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;
as well as URLs for NNTP newsgroup(s).