linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] detached cloning
Date: Thu, 10 Apr 2003 11:12:48 -0400	[thread overview]
Message-ID: <20030410151248.GA11647@nevyn.them.org> (raw)
In-Reply-To: <20030409232931.GA15917@werewolf.able.es>

On Thu, Apr 10, 2003 at 01:29:31AM +0200, J.A. Magallon wrote:
> 
> On 04.08, Daniel Jacobowitz wrote:
> > On Sun, Apr 06, 2003 at 01:09:44AM +0200, J.A. Magallon wrote:
> > > 
> > > On 04.06, J.A. Magallon wrote:
> > > > 
> > > > On 04.04, Marcelo Tosatti wrote:
> > > > > 
> > > > > So here goes -pre7. Hopefully the last -pre.
> > > > > 
> > > > 
> > > 
> > > Fix a crash that can be caused by a CLONE_DETACHED thread.
> > > Author: Ingo Molnar <mingo@elte.hu>
> > > 
> [...]
> > 
> > CLONE_DETACHED isn't even in 2.4 except in Red Hat kernels.
> > 
> 
> But pthreads can spawn detached threads. Can this have any effect ?

Detached threads actually have no relationship to CLONE_DETACHED.  In
NPTL all threads are CLONE_DETACHED whether they're detached or not; in
LinuxThreads they never are, also regardless.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-04-10 15:01 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 21:15 Linux 2.4.21-pre7 Marcelo Tosatti
2003-04-04 21:34 ` J.A. Magallon
2003-04-04 21:01   ` Alan Cox
2003-04-04 22:44 ` kernel
2003-04-05  0:31 ` J.A. Magallon
2003-04-05 16:55   ` Alan Cox
2003-04-05  0:43 ` J.A. Magallon
2003-04-05  0:50   ` [PATCH] AT_PLATFORM on HT-P4 J.A. Magallon
2003-04-05  1:18     ` Benjamin LaHaise
2003-04-05  1:22       ` J.A. Magallon
2003-04-05  1:24         ` Benjamin LaHaise
2003-04-05  0:50   ` [PATCH] redundant printk decl J.A. Magallon
2003-04-05  0:52   ` [PATCH] thread signaling J.A. Magallon
2003-04-05 16:53     ` Alan Cox
2003-04-05  0:53   ` [PATCH] detached clone J.A. Magallon
2003-04-05  0:55   ` [PATCH] e1000 close J.A. Magallon
2003-04-05  2:06   ` Linux 2.4.21-pre7 Marcelo Tosatti
2003-04-05  0:51 ` Nathan Poznick
2003-04-05  3:52 ` Linux 2.4.21-pre7 - hpt366.c does not build Eyal Lebedinsky
2003-04-21 16:33   ` Marcelo Tosatti
2003-04-05 16:03 ` Linux 2.4.21-pre7 Udo A. Steinberg
2003-04-05 21:49 ` Jerome Chantelauze
2003-04-05 22:42 ` J.A. Magallon
2003-04-05 23:02   ` [PATCH] AT_PLATFORM on HT-P4 J.A. Magallon
2003-04-05 23:03   ` Linux 2.4.21-pre7 J.A. Magallon
2003-04-05 23:06   ` [PATCH] config/dep bugs J.A. Magallon
2003-04-06 22:18     ` Karl Weigel
2003-04-05 23:08   ` [PATCH] thread signaling J.A. Magallon
2003-04-05 23:09   ` [PATCH] detached cloning J.A. Magallon
2003-04-07 23:13     ` Daniel Jacobowitz
2003-04-09 23:29       ` J.A. Magallon
2003-04-10 15:12         ` Daniel Jacobowitz [this message]
2003-04-05 23:12   ` [PATCH] e1000 close J.A. Magallon
2003-04-06 14:53     ` Alan Cox
2003-04-08 16:28 ` Linux 2.4.21-pre7 Kaj-Michael Lang
2003-04-09  9:55   ` mikpe
2003-04-09 10:09     ` Benjamin Herrenschmidt
2003-04-09 10:20       ` mikpe
2003-04-09 11:01         ` Benjamin Herrenschmidt
2003-04-09 14:27         ` Ruth Ivimey-Cook

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=20030410151248.GA11647@nevyn.them.org \
    --to=dan@debian.org \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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).