All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Zeuner, Axel" <Axel.Zeuner@partner.commerzbank.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Thread group exit
Date: Tue, 06 Aug 2002 10:23:19 -0700	[thread overview]
Message-ID: <3D500607.78A11BFD@mvista.com> (raw)
In-Reply-To: 1028544328.17780.18.camel@irongate.swansea.linux.org.uk

Alan Cox wrote:
> 
> On Mon, 2002-08-05 at 09:58, Zeuner, Axel wrote:
> > I would expect, that changes of the parent of one member of the thread group
> > do not affect the interactions between the members of the group.
> > Corrections are welcome.
> > (Please cc mails to me, I read only the archives of the
> > linux-kernel list.)
> 
> I agree with your diagnosis I'm not convinced by your change. The thread
> groups are only used by NGPT not by glibc pthreads while the problem is
> true across both.

Have the glibc folks decided NOT to move to thread groups? 
I sort of expected that they were just taking their time,
but would eventually move.

-g
> 
> Possibly the right fix is to remove the reparent to init increment of
> self_exec_id and instead explicitly check process 1 in the signal paths.
> 
> Opinions ?
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Real time sched:  http://sourceforge.net/projects/rtsched/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

  reply	other threads:[~2002-08-06 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05  8:58 Thread group exit Zeuner, Axel
2002-08-05 10:45 ` Alan Cox
2002-08-06 17:23   ` george anzinger [this message]
2002-08-06 18:54     ` Alan Cox

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=3D500607.78A11BFD@mvista.com \
    --to=george@mvista.com \
    --cc=Axel.Zeuner@partner.commerzbank.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.