linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Richard J Moore <richardj_moore@uk.ibm.com>
Cc: Rob Landley <landley@trommello.org>,
	linux-kernel@vger.kernel.org,
	S Vamsikrishna <vamsi_krishna@in.ibm.com>,
	Werner Almesberger <wa@almesberger.net>
Subject: Re: 2.4 Ready list - Kernel Hooks
Date: Wed, 23 Oct 2002 10:09:53 -0700	[thread overview]
Message-ID: <20021023170952.GF13539@kroah.com> (raw)
In-Reply-To: <OF8955D2C4.965253CB-ON80256C5B.002C9AA3@portsmouth.uk.ibm.com>

On Wed, Oct 23, 2002 at 09:10:13AM +0100, Richard J Moore wrote:
> 
> >On Wed, Oct 23, 2002 at 12:09:38AM +0100, Richard J Moore wrote:
> >> We created
> >> kernel hooks for exactly the same reasons that LSM needs hooks - to allow
> >> ancillary function to exist outside the kernel, to avoid kernel bloat, to
> >> allow more than one function to be called from a given call-back (think of
> >> kdb and kprobes - both need to be called from do_debug).
> >
> >No, that is NOT the same reason LSM needs hooks!  LSM hooks are there to
> >mediate access to various kernel objects, from within the kernel itself.
> >Please do not confuse LSM with any of the above projects.
> 
> I would have to understand what you meant by "mediate between various
> kernel objects" to know whether LSM's need for hooks is radically different
> to RAS needs. Can you explain further?

Please read the LSM documentation for more information about this.  It
can be found in the kernel at:
	Documentation/DocBook/lsm.*
and there are a number of USENIX and OLS papers about different aspects
of the project at:
	lsm.immunix.org

In the beginning of the LSM project, both the DProbes and LTT groups
came asking that we use their patches to implement LSM.  It was
quickly determined that the types of "hooks" these projects offered was
not what the LSM group needed (or wanted).  So the current
implementation was developed.

Hope this helps.  If you have any further questions, please feel free to
ask (after reading that documentation :)

thanks,

greg k-h

  reply	other threads:[~2002-10-23 17:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  8:10 2.4 Ready list - Kernel Hooks Richard J Moore
2002-10-23 17:09 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-24 16:38 Richard J Moore
2002-10-24 17:02 ` Greg KH
2002-10-23 16:47 Richard J Moore
2002-10-23 19:50 ` Werner Almesberger
2002-10-24  7:38   ` Vamsi Krishna S .
2002-10-24 17:22     ` Werner Almesberger
2002-10-22 23:09 Richard J Moore
2002-10-22 23:54 ` Greg KH
2002-10-23 15:28 ` Werner Almesberger
2002-10-23 16:21   ` Karim Yaghmour
2002-10-21 12:24 Richard J Moore
2002-10-22 21:02 ` Werner Almesberger

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=20021023170952.GF13539@kroah.com \
    --to=greg@kroah.com \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardj_moore@uk.ibm.com \
    --cc=vamsi_krishna@in.ibm.com \
    --cc=wa@almesberger.net \
    /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).