Re: crypto api initialized late

[Chris Wright]

* Reiner Sailer (sailer@xxxxxxxxxx) wrote:
> Chris Wright <chrisw@xxxxxxxx> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/