Date: Tue, 13 May 2003 07:03:36 +0200
From: Andi Kleen <ak@suse.de>
To: linux-kernel@vger.kernel.org, hch@infradead.org, gregkh@kroah.com,
       linux-security-module@wirex.com, ak@suse.de
Subject: Re: [PATCH] Early init for security modules
Message-ID: <20030513050336.GA10596@Wotan.suse.de>
References: <20030512200309.C20068@figure1.int.wirex.com> <20030512201518.X19432@figure1.int.wirex.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030512201518.X19432@figure1.int.wirex.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1030
Lines: 21

On Mon, May 12, 2003 at 08:15:18PM -0700, Chris Wright wrote:
> * Chris Wright (chris@wirex.com) wrote:
> > As discussed before, here is a simple patch to allow for early
> > initialization of security modules when compiled statically into the
> > kernel.  The standard do_initcalls is too late for complete coverage of
> > all filesystems and threads for example.  If this looks OK, I'd like to
> > push it on to Linus.  Patch is against 2.5.69-bk.  It is tested on i386,
> > and various arch maintainers are copied on relevant bits of patch.
> 
> This is just the arch specific linker bits for the early initialization
> for security modules patch.  Does this look sane for this arch?

It would work for x86-64. But why can't you use core_initcall() or 
postcore_initcall() ? 

-Andi
-
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/