linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Milan Broz <mbroz@redhat.com>,
	Tvrtko Ursulin <tvrtko@ursulin.net>,
	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 21:35:35 +0100	[thread overview]
Message-ID: <20121030203535.GY639@pengutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1210301856390.2756@ionos>

Hello,

On Tue, Oct 30, 2012 at 06:57:37PM +0100, Thomas Gleixner wrote:
> On Tue, 30 Oct 2012, 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.
> 
> Grrr. So I forgot top zap the one Peter added. Stupid me.
>  
> > This cause a failure in initialization of larval algorithms,
> > like e.g. cbc(aes).
> 
> Thanks for spotting!
This patch fixes booting my laptop. But now it hangs after login.

thanks
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
--
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

  reply	other threads:[~2012-10-30 20:35 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                           ` [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 [this message]
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=20121030203535.GY639@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --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=tglx@linutronix.de \
    --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).