mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm1
Date: Mon, 10 May 2004 16:28:18 -0700	[thread overview]
Message-ID: <20040510162818.376b4a55.akpm@osdl.org> (raw)
In-Reply-To: <20040510231146.GA5168@taniwha.stupidest.org>

Chris Wedgwood <cw@f00f.org> wrote:
>
> On Mon, May 10, 2004 at 03:02:03PM -0700, Andrew Morton wrote:
> 
> > Capabilities are broken and don't work.  Nobody has a clue how to
> > provide the required services with SELinux and nobody has any code
> > and we need the feature *now* before vendors go shipping even more
> > ghastly stuff.
> 
> eh? magic groups are nasty...  and why is this needed?  can't
> oracle/whatever just run with a wrapper to give the capabilities out
> as required until a better solution is available

capabilities all get dropped on the floor across exec().  We discussed this
on this list after Bill and I spent half a day getting cap_pam working,
only to discover that the kernel had been nobbled years ago.

> and who cares if vendors show something worse?

me.

>  vendors ship crap all
> the time, that's partly why we have vendor kernels --- to ship crap
> that people want now w/o having to corrupt and pollute the cleanliness
> of the mainline kernel until a sufficiently well thought out sane plan
> can be devised

If vendors are forced to ship a nasty hack it often points at problems in
the mainline kernel.  Certainly that's true in this case.

And if we are unable to fix the kernel acceptably then I'd prefer that the
expedient fix be in the mainstream kernel so as to prevent divergence in
user-visible features between vendor kernels.

And let's remember, code-wise, this is a very small change.

If someone comes up with an acceptable SELinux (or whatever)-based solution
then fine.  But it's too late.  This stuff is going out the door to end 2.6
users and that's just tough luck.  The least we can do is to ensure that it
works the same across different vendor's kernels.


  parent reply	other threads:[~2004-05-10 23:32 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-10  9:45 2.6.6-mm1 Andrew Morton
2004-05-10 10:52 ` 2.6.6-mm1 Dominik Karall
2004-05-10 11:18   ` 2.6.6-mm1 Dave Jones
2004-05-10 12:20     ` 2.6.6-mm1 Nick Piggin
2004-05-10 12:22       ` 2.6.6-mm1 Dave Jones
2004-05-10 12:35 ` 2.6.6-mm1: FB_ASILIANT: no help text Adrian Bunk
2004-05-10 12:45 ` 2.6.6-mm1: a different CONFIG_STANDALONE approach Adrian Bunk
2004-05-10 12:57   ` Adrian Bunk
2004-05-10 20:00   ` Andrew Morton
2004-05-10 14:38 ` 2.6.6-mm1 Norberto Bensa
2004-05-10 14:55   ` 2.6.6-mm1 Dominik Karall
2004-05-10 15:02     ` 2.6.6-mm1 Norberto Bensa
2004-05-10 15:22       ` 2.6.6-mm1 Dominik Karall
2004-05-10 15:33         ` 2.6.6-mm1 Norberto Bensa
2004-05-10 15:20 ` 2.6.6-mm1 Christoph Hellwig
2004-05-11  5:21   ` 2.6.6-mm1 Andrew Morton
2004-05-10 21:37 ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 22:02   ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:05     ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 22:15       ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:20         ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 22:47           ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:48             ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:16         ` 2.6.6-mm1 Matt Mackall
2004-05-10 22:27     ` 2.6.6-mm1 Valdis.Kletnieks
2004-05-10 22:48       ` 2.6.6-mm1 Andrew Morton
2004-05-10 23:01         ` 2.6.6-mm1 Valdis.Kletnieks
2004-05-10 23:11     ` 2.6.6-mm1 Chris Wedgwood
2004-05-10 23:14       ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:28       ` Andrew Morton [this message]
2004-05-10 23:33         ` 2.6.6-mm1 Chris Wedgwood
2004-05-10 23:51           ` 2.6.6-mm1 Andrew Morton
2004-05-10 23:53             ` 2.6.6-mm1 Chris Wedgwood
2004-05-11  0:14               ` 2.6.6-mm1 Andrew Morton
2004-05-11  0:24                 ` 2.6.6-mm1 Wim Coekaerts
2004-05-11  1:10                   ` 2.6.6-mm1 Andrew Morton
2004-05-11  1:51                     ` 2.6.6-mm1 Wim Coekaerts
2004-05-11  6:23                       ` 2.6.6-mm1 Christoph Hellwig
2004-05-12  2:44                         ` 2.6.6-mm1 Andrea Arcangeli
2004-05-12  5:11                           ` 2.6.6-mm1 Chris Wedgwood
2004-05-11 15:12                       ` 2.6.6-mm1 Wim Coekaerts
2004-05-12  5:42                         ` 2.6.6-mm1 Christoph Hellwig
2004-05-12  5:50                           ` 2.6.6-mm1 Christoph Hellwig
2004-05-11  6:22                     ` 2.6.6-mm1 Christoph Hellwig
2004-05-11  6:21                 ` 2.6.6-mm1 Christoph Hellwig
2004-05-11  6:37                   ` 2.6.6-mm1 William Lee Irwin III
2004-05-11  6:18             ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:33       ` 2.6.6-mm1 Chris Wright
2004-05-11  1:59         ` 2.6.6-mm1 Matt Mackall
2004-05-11 14:34   ` 2.6.6-mm1 Stephen Smalley
2004-05-11 16:48     ` 2.6.6-mm1 Chris Wright
2004-05-12 12:49 ` 2.6.6-mm1 Sean Neakums
2004-05-12 19:26   ` 2.6.6-mm1 Andrew Morton
2004-05-10 12:43 2.6.6-mm1 Sid Boyce
2004-05-12  8:13 ` 2.6.6-mm1 Andrew Morton
2004-05-10 16:50 2.6.6-mm1 Sid Boyce
     [not found] <fa.j4d62qo.1144tpk@ifi.uio.no>
     [not found] ` <fa.gg699ad.b2omr9@ifi.uio.no>
2004-05-11  6:33   ` 2.6.6-mm1 Andy Lutomirski
2004-05-11 10:34 2.6.6-mm1 Sid Boyce
2004-05-11 14:49 2.6.6-mm1 Neil Schemenauer
2004-05-11 18:55 ` 2.6.6-mm1 Andrew Morton
2004-05-12 12:26 2.6.6-mm1 Sid Boyce
2004-05-12 15:27 2.6.6-mm1 Sid Boyce

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=20040510162818.376b4a55.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=cw@f00f.org \
    --cc=hch@infradead.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®