All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Reiner Sailer <sailer@us.ibm.com>
Cc: Chris Wright <chrisw@osdl.org>,
	davem@davemloft.net, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: crypto api initialized late
Date: Mon, 16 May 2005 13:40:03 -0700	[thread overview]
Message-ID: <20050516204003.GV27549@shell0.pdx.osdl.net> (raw)
In-Reply-To: <OFBC11B5F7.2600BE34-ON85257003.006F5006-85257003.0070115B@us.ibm.com>

* Reiner Sailer (sailer@us.ibm.com) wrote:
> Chris Wright <chrisw@osdl.org> wrote on 05/16/2005 04:03:17 PM:
> > I'm surprised this helps at all.  Does this mean you are not using
> > security_initcall() in your module?
> 
> I use simply __initcall, which is the same level as the 
> module_initcall used in the crypto functions (sha1.c). Looking into 
> init.h, security_initcall should resolve to __initcall as well.

If you are compiling as a module (assuming that's not the case here),
then it's a normal module_init.  Otherwise it's put in it's own text
segment, and called during security_init(),  which is earlier than
do_inticalls() to ensure all objects get labeled.

> Changing the compile sequence orders, the crypto init and sha1 
> registration happens just ahead of my security module because
> (so I assume) the order of the compilation determines the order
> of the init calls inside the same initcall block.

Yes, it does.

thanks,
-chris

  parent reply	other threads:[~2005-05-16 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 19:15 crypto api initialized late Reiner Sailer
2005-05-16 20:03 ` Chris Wright
     [not found]   ` <OFBC11B5F7.2600BE34-ON85257003.006F5006-85257003.0070115B@us.ibm.com>
2005-05-16 20:40     ` Chris Wright [this message]
2005-05-16 20:18 ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2005-05-16 20:30 Reiner Sailer

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=20050516204003.GV27549@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sailer@us.ibm.com \
    /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.