LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: legoater@free.fr, linux-kernel@vger.kernel.org,
	containers@lists.osdl.org, xemul@openvz.org
Subject: Re: [PATCH 2/2] extend clone_flags using parent_tidptr argument
Date: Mon, 4 Feb 2008 13:38:10 -0800	[thread overview]
Message-ID: <20080204133810.0077ec0d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080204202416.GA26422@sergelap.austin.ibm.com>

On Mon, 4 Feb 2008 14:24:16 -0600
"Serge E. Hallyn" <serue@us.ibm.com> wrote:

> Quoting Cedric Le Goater (legoater@free.fr):
> > From: Cedric Le Goater <clg@fr.ibm.com>
> >
> > We have at least 2 patchsets requiring each a new clone flag and there it 
> > is, we've reached the limit, none are left.  
> > This patch uses the CLONE_DETACHED flag (unused) as a marker to extend the 
> 
> Are we pretty sure that there is no legacy software out there which has
> continued to specify CLONE_DETACHED since the kernel ignores it?

Please see -mm's
clone-prepare-to-recycle-clone_detached-and-clone_stopped.patch

That patch has been cut back to only recycle CLONE_STOPPED because there
indeed was software out there which is setting CLONE_DETACHED.

See http://linux.derkeiler.com/Mailing-Lists/Kernel/2007-11/msg04293.html


  reply	other threads:[~2008-02-04 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 17:27 [PATCH 2/2] extend clone_flags using parent_tidptr argument Cedric Le Goater
2008-02-04 20:24 ` Serge E. Hallyn
2008-02-04 21:38   ` Andrew Morton [this message]
2008-02-05  8:20     ` Cedric Le Goater

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=20080204133810.0077ec0d.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=containers@lists.osdl.org \
    --cc=legoater@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    --cc=xemul@openvz.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;
as well as URLs for NNTP newsgroup(s).