mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "LA Walsh" <law@tlinx.org>
To: <linux-kernel@vger.kernel.org>
Subject: RE: lsm truly "generic" allowing complete choice?  Clean? Simple? Idon't think so.
Date: Wed, 12 Feb 2003 01:58:53 -0800	[thread overview]
Message-ID: <004301c2d27d$5997c9e0$1403a8c0@sc.tlinx.org> (raw)
In-Reply-To: <200302121010.56366.russell@coker.com.au>

> From: Russell Coker
> linux-kernel mailing list removed from the CC list (again), they've 
> probably heard too much of this discussion already.  
---
	It was isolation away from the mainline kernel list that allowed
the current patchwork design.  Attempts to clarify the LSM list charter
which ended up on lkml resulted in movements to silence those 
questioning the emperor's new clothes (or lack thereof).  LSM project
members want their changes in the kernel code *today*.  It is appropriate
to discuss design methodolgy on the kernel list since design
methodology discussion was forbidden on lkml as was any interaction 
with the linux community.  Quite frankly, the brown-nosing, back-slapping
politics really put a bitter taste on things that were naively believed
to be based more on technocracy than making people 'look good' and
commercial self-interest.

> If making the DAC code a module slows down non-LSM servers 
> and takes a lot of 
> programmer time to implement, is it a useful effort?
---

	It was already done -- the mainline kernel modules were done in
about 2 person-months of motivated programmer time.   There was no measured slowdown of non-LSM servers.  Changes done earlier by
the same project
lead of that project had all changes in the mainline kernel code compile
to nothing when compiled out.  Performance was a consideration in the
implementation.

-l


       reply	other threads:[~2003-02-12  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200302121010.56366.russell@coker.com.au>
2003-02-12  9:58 ` LA Walsh [this message]
2003-02-12 11:41   ` Christoph Hellwig

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='004301c2d27d$5997c9e0$1403a8c0@sc.tlinx.org' \
    --to=law@tlinx.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®