mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: CLONE_DETACHED
Date: Fri, 16 Jan 2004 18:26:32 -0800	[thread overview]
Message-ID: <20040116182632.7890fe93.akpm@osdl.org> (raw)
In-Reply-To: <UTC200401170217.i0H2HNt16225.aeb@smtp.cwi.nl>

Andries.Brouwer@cwi.nl wrote:
>
> My current version of the clone.2 manual page says
> 
>        CLONE_THREAD
>               (Linux 2.4 onwards) If  CLONE_THREAD  is  set,  the
>               child  is  placed  in  the same thread group as the
>               calling process.  Now in 2.6 also  the  meaningless
>               CLONE_DETACHED  (introduced in 2.5.32) must be set.
> 
> I wonder whether it is too late to remove CLONE_DETACHED entirely.
> There are precisely two occurrences: the definition and the check
> that it is set when CLONE_THREAD is set. Seems fairly useless.
> 

Changelog says:

ChangeSet 1.1150 2003/08/14 11:11:39 torvalds@home.osdl.org
  Mark CLONE_DETACHED as being irrelevant: it must match CLONE_THREAD.
  
  CLONE_THREAD without CLONE_DETACHED will now return -EINVAL, and
  for a while we will warn about anything that uses it (there are no
  known users, but this will help pinpoint any problems if somebody
  used to care about the invalid combination).


It has been five months; I'd say we could lose it now.  Linus?

      reply	other threads:[~2004-01-17  2:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17  2:17 CLONE_DETACHED Andries.Brouwer
2004-01-17  2:26 ` Andrew Morton [this message]

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=20040116182632.7890fe93.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

Powered by JetHome