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
Date: Tue, 13 May 2003 07:03:36 +0200 [thread overview]
Message-ID: <20030513050336.GA10596@Wotan.suse.de> (raw)
In-Reply-To: <20030512201518.X19432@figure1.int.wirex.com>
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
next prev parent reply other threads:[~2003-05-13 4:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 3:03 [PATCH] Early init for security modules Chris Wright
2003-05-13 3:07 ` Chris Wright
2003-05-13 3:08 ` Chris Wright
2003-05-13 9:03 ` Russell King
2003-05-13 9:20 ` Documentation/linu-logo-HOWTO.txt cosmos
2003-05-13 9:57 ` Documentation/linu-logo-HOWTO.txt Geert Uytterhoeven
2003-05-13 11:25 ` Documentation/linux-logo-HOWTO.txt cosmos
2003-05-13 13:16 ` Documentation/linu-logo-HOWTO.txt Alan Cox
2003-05-13 3:08 ` [PATCH] Early init for security modules Chris Wright
2003-05-13 3:09 ` Chris Wright
2003-05-13 3:09 ` Chris Wright
2003-05-13 5:56 ` David Mosberger
2003-05-13 3:10 ` Chris Wright
2003-05-13 3:10 ` Chris Wright
2003-05-14 0:10 ` Greg Ungerer
2003-05-13 3:11 ` Chris Wright
2003-05-13 3:12 ` Chris Wright
2003-05-13 3:13 ` Chris Wright
2003-05-13 3:13 ` Chris Wright
2003-05-13 4:45 ` Paul Mackerras
2003-05-13 3:13 ` Chris Wright
2003-05-13 3:14 ` Chris Wright
2003-05-13 3:14 ` Chris Wright
2003-05-13 3:15 ` Chris Wright
2003-05-13 5:03 ` Andi Kleen [this message]
2003-05-13 5:20 ` Chris Wright
2003-05-13 5:27 ` Christoph Hellwig
2003-05-20 0:57 ` Chris Wright
2003-05-13 5:28 ` Andi Kleen
2003-05-13 6:16 ` Chris Wright
2003-05-13 6:29 ` Andi Kleen
2003-05-13 18:07 ` Sam Ravnborg
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=20030513050336.GA10596@Wotan.suse.de \
--to=ak@suse.de \
--cc=gregkh@kroah.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.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 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).