From: Chris Wright <chris@wirex.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, hch@infradead.org, greg@kroah.com,
linux-security-module@wirex.com
Subject: Re: [PATCH] Early init for security modules
Date: Mon, 12 May 2003 23:16:55 -0700 [thread overview]
Message-ID: <20030512231655.B21486@figure1.int.wirex.com> (raw)
In-Reply-To: <20030513052832.GF10596@Wotan.suse.de>; from ak@suse.de on Tue, May 13, 2003 at 07:28:33AM +0200
* Andi Kleen (ak@suse.de) wrote:
> On Mon, May 12, 2003 at 10:20:00PM -0700, Chris Wright wrote:
> >
> > This is too late. Those are just for order in do_initcalls() which is
> > well after some kernel threads have been created and filesystems have been
> > mounted, etc. This patch allows statically linked modules to catch
> > the creation of such kernel objects and give them all consistent labels.
>
> I would give them a generic name then in case someone else needs that too,
> like "early_initcalls"
I orginally thought it would be nice to make it generic, but it's
location is somewhat specific to the security hooks. It seems there is
easily tension between conflicting needs, should be earlier...should be
later, so I made it specific. Is there currently a need?
thanks,
chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2003-05-13 6:05 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
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 [this message]
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=20030512231655.B21486@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=ak@suse.de \
--cc=greg@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).