public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: David Howells <dhowells@redhat.com>,
	Andreas Gruenbacher <agruen@suse.de>,
	"Andrew G. Morgan" <morgan@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] file capabilities: Add no_file_caps switch
Date: Wed, 27 Aug 2008 19:48:08 -0500	[thread overview]
Message-ID: <20080828004807.GC16607@us.ibm.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0808281004170.18937@tundra.namei.org>

Quoting James Morris (jmorris@namei.org):
> On Wed, 27 Aug 2008, David Howells wrote:
> 
> >  (2) Neuter sys_capset().  I've been holding this off for the next merge
> >      window as it isn't a bugfix, unlike (1).  Perhaps I should ask James to
> >      push it to Linus.  James?
> 
> Linus only pulled the PF_SUPERPRIV fix once the sys_capset change was 
> removed from the patch.  It really does need to be a bugfix at this stage.

Ok, sorry, of course that makes sense.  I was just confused about where
the patch was originally heading.

Would it be appropriate to put the capset neutering patch in your
security-testing tree, James, or does that feed straight into
linux-next?

thanks,
-serge

  reply	other threads:[~2008-08-28  0:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 18:57 [patch] file capabilities: Add no_file_caps switch Andreas Gruenbacher
2008-08-26 20:28 ` Ingo Molnar
2008-08-27 13:52 ` Serge E. Hallyn
2008-08-27 15:29   ` Andreas Gruenbacher
2008-08-27 16:04     ` Serge E. Hallyn
2008-08-27 16:13       ` David Howells
2008-08-27 16:32         ` Alan Cox
2008-08-27 17:00           ` David Howells
2008-08-27 16:57       ` Andreas Gruenbacher
2008-08-27 17:04         ` David Howells
2008-08-27 18:58         ` Serge E. Hallyn
2008-08-27 21:14           ` David Howells
2008-08-28  0:05             ` James Morris
2008-08-28  0:48               ` Serge E. Hallyn [this message]
2008-08-28  1:57                 ` James Morris
2008-08-28 15:35           ` Andrew G. Morgan
2008-08-28 17:09             ` Serge E. Hallyn
2008-08-28 16:27           ` Andreas Gruenbacher

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=20080828004807.GC16607@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=agruen@suse.de \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morgan@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