The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: sukadev@us.ibm.com
Cc: linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	serue@us.ibm.com, haveblue@us.ibm.com,
	Containers <containers@lists.osdl.org>,
	clg@fr.ibm.com
Subject: Re: [PATCH] Define CLONE_NEWPID flag
Date: Wed, 21 Mar 2007 13:39:38 -0700	[thread overview]
Message-ID: <20070321133938.bff535a3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070321194103.GA29820@us.ibm.com>

On Wed, 21 Mar 2007 12:41:03 -0700
sukadev@us.ibm.com wrote:

> 
> This was discussed on containers and we thought it would be useful
> to reserve this flag.
> ---
> 
> From: Sukadev Bhattiprolu <sukadev@us.ibm.com>
> Subject: [PATCH] Define CLONE_NEWPID flag
> 
> Define CLONE_NEWPID flag that will be used to clone pid namespaces.
> 
> Signed-off-by: Sukadev Bhattiprolu <sukadev@us.ibm.com>
> ---
>  include/linux/sched.h |    1 +
>  1 file changed, 1 insertion(+)
> 
> Index: lx26-21-rc3-mm2/include/linux/sched.h
> ===================================================================
> --- lx26-21-rc3-mm2.orig/include/linux/sched.h	2007-03-20 20:13:19.000000000 -0700
> +++ lx26-21-rc3-mm2/include/linux/sched.h	2007-03-21 11:10:33.000000000 -0700
> @@ -26,6 +26,7 @@
>  #define CLONE_STOPPED		0x02000000	/* Start in stopped state */
>  #define CLONE_NEWUTS		0x04000000	/* New utsname group? */
>  #define CLONE_NEWIPC		0x08000000	/* New ipcs */
> +#define CLONE_NEWPID		0x10000000      /* New pid namespace */
>  

Do we actually have any need to reserve it at this time?  I'd have thought
that we could defer adding this until we have some code in-kernel which
uses it.


  reply	other threads:[~2007-03-21 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 19:41 [PATCH] Define CLONE_NEWPID flag sukadev
2007-03-21 20:39 ` Andrew Morton [this message]
2007-03-21 20:57   ` Eric W. Biederman
2007-03-23  1:36   ` Herbert Poetzl

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=20070321133938.bff535a3.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    --cc=sukadev@us.ibm.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