Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261875AbVEPUkf (ORCPT ); Mon, 16 May 2005 16:40:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261168AbVEPUke (ORCPT ); Mon, 16 May 2005 16:40:34 -0400 Received: from fire.osdl.org ([65.172.181.4]:26045 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261872AbVEPUkV (ORCPT ); Mon, 16 May 2005 16:40:21 -0400 Date: Mon, 16 May 2005 13:40:03 -0700 From: Chris Wright To: Reiner Sailer Cc: Chris Wright , davem@davemloft.net, herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: crypto api initialized late Message-ID: <20050516204003.GV27549@shell0.pdx.osdl.net> References: <20050516200317.GD23013@shell0.pdx.osdl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1200 Lines: 28 * Reiner Sailer (sailer@us.ibm.com) wrote: > Chris Wright 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/