[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070321133938.bff535a3.akpm@linux-foundation.org>
Date: Wed, 21 Mar 2007 13:39:38 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: sukadev@...ibm.com
Cc: linux-kernel@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>, serue@...ibm.com,
haveblue@...ibm.com, Containers <containers@...ts.osdl.org>,
clg@...ibm.com
Subject: Re: [PATCH] Define CLONE_NEWPID flag
On Wed, 21 Mar 2007 12:41:03 -0700
sukadev@...ibm.com wrote:
>
> This was discussed on containers and we thought it would be useful
> to reserve this flag.
> ---
>
> From: Sukadev Bhattiprolu <sukadev@...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@...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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists