From: Tvrtko Ursulin <tvrtko@ursulin.net>
To: Milan Broz <mbroz@redhat.com>
Cc: dm-crypt@saout.de, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org, okozina@redhat.com,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [dm-crypt] [PATCH] Fix crypto api init for 3.6.4-rt10
Date: Tue, 30 Oct 2012 18:24:50 +0000 [thread overview]
Message-ID: <50901B72.6090201@ursulin.net> (raw)
In-Reply-To: <508FF1D6.3030900@redhat.com>
Hi,
On 30/10/12 15:27, Milan Broz wrote:
> Fix crypto api for 3.6.4-rt10 (broken only in realtime patchset)
>
> In peterz-srcu-crypto-chain.patch the blocking notifier is changed
> to srcu notifier and added initialization to module init fucntion.
>
> Later, in crypto-make-core-static-and-init-scru-early.patch, is that
> initialization added also to core_initcall().
>
> This patch removes crypto_chain init from algapi initialization,
> because this function is called later and already initialized
> cryptomgr notifier is lost.
>
> This cause a failure in initialization of larval algorithms,
> like e.g. cbc(aes).
Thanks for the quick fix!
Tvrtko
WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko@ursulin.net>
To: Milan Broz <mbroz@redhat.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-rt-users@vger.kernel.org, dm-crypt@saout.de,
linux-kernel@vger.kernel.org, okozina@redhat.com
Subject: Re: [PATCH] Fix crypto api init for 3.6.4-rt10
Date: Tue, 30 Oct 2012 18:24:50 +0000 [thread overview]
Message-ID: <50901B72.6090201@ursulin.net> (raw)
In-Reply-To: <508FF1D6.3030900@redhat.com>
Hi,
On 30/10/12 15:27, Milan Broz wrote:
> Fix crypto api for 3.6.4-rt10 (broken only in realtime patchset)
>
> In peterz-srcu-crypto-chain.patch the blocking notifier is changed
> to srcu notifier and added initialization to module init fucntion.
>
> Later, in crypto-make-core-static-and-init-scru-early.patch, is that
> initialization added also to core_initcall().
>
> This patch removes crypto_chain init from algapi initialization,
> because this function is called later and already initialized
> cryptomgr notifier is lost.
>
> This cause a failure in initialization of larval algorithms,
> like e.g. cbc(aes).
Thanks for the quick fix!
Tvrtko
next prev parent reply other threads:[~2012-10-30 18:24 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
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 ` Tvrtko Ursulin [this message]
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=50901B72.6090201@ursulin.net \
--to=tvrtko@ursulin.net \
--cc=dm-crypt@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=okozina@redhat.com \
--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.