linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <ak@suse.de>,
	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: Tue, 13 May 2003 06:27:48 +0100	[thread overview]
Message-ID: <20030513062748.A2677@infradead.org> (raw)
In-Reply-To: <20030512222000.A21486@figure1.int.wirex.com>; from chris@wirex.com on Mon, May 12, 2003 at 10:20:00PM -0700

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.

Patch looks fine to me.  Could you please make the initcalls mandatory for security
modules and remove the module exports for the regioster functions so peop can't
do the crappy check for each module whether it's already initialized stuff the early selinux
for LSM versions did?

  reply	other threads:[~2003-05-13  5:15 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 [this message]
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=20030513062748.A2677@infradead.org \
    --to=hch@infradead.org \
    --cc=ak@suse.de \
    --cc=greg@kroah.com \
    --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).