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
Subject: [PATCH] Fix crypto api init for 3.6.4-rt10
Date: Tue, 30 Oct 2012 16:27:18 +0100 [thread overview]
Message-ID: <508FF1D6.3030900@redhat.com> (raw)
In-Reply-To: <508FA405.2050509@redhat.com>
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).
Signed-off-by: Milan Broz <mbroz@redhat.com>
--- crypto/algapi.c.old 2012-10-30 16:11:23.000000000 +0100
+++ crypto/algapi.c 2012-10-30 16:12:14.988847944 +0100
@@ -956,7 +956,6 @@ EXPORT_SYMBOL_GPL(crypto_xor);
static int __init crypto_algapi_init(void)
{
- srcu_init_notifier_head(&crypto_chain);
crypto_init_proc();
return 0;
}
next prev parent reply other threads:[~2012-10-30 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50830D33.5050807@ursulin.net>
[not found] ` <5083C61C.5090807@gmail.com>
[not found] ` <5083E4A8.3060501@ursulin.net>
[not found] ` <5083E87B.2080908@gmail.com>
[not found] ` <5083EC61.8070505@ursulin.net>
[not found] ` <50844D01.9090805@gmail.com>
[not found] ` <5084551E.5040304@ursulin.net>
[not found] ` <508ED985.5060301@ursulin.net>
[not found] ` <508EDD6E.7030908@gmail.com>
[not found] ` <508EE395.9010709@ursulin.net>
[not found] ` <508EE395.9010709-9sj9WOxYP5jR7s880joybQ@public.gmane.org>
2012-10-29 20:45 ` cryptsetup not working under 3.6 - RT patch set seem to break it Tvrtko Ursulin
2012-10-29 23:51 ` [dm-crypt] " Thomas Gleixner
2012-10-30 9:40 ` Uwe Kleine-König
2012-10-30 9:55 ` Milan Broz
2012-10-30 15:27 ` Milan Broz [this message]
2012-10-30 17:57 ` [PATCH] Fix crypto api init for 3.6.4-rt10 Thomas Gleixner
2012-10-30 20:35 ` Uwe Kleine-König
2012-10-30 18:24 ` Tvrtko Ursulin
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=508FF1D6.3030900@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--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 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).