From: Andreas Dilger <adilger@turbolabs.com>
To: Terje Eggestad <terje.eggestad@scali.no>
Cc: Elan Feingold <efeingold@mn.rr.com>, linux-kernel@vger.kernel.org
Subject: Re: Multithreaded core dumps (CLONE_THREAD and elf)
Date: Thu, 30 Aug 2001 03:19:18 -0600 [thread overview]
Message-ID: <20010830031918.H541@turbolinux.com> (raw)
In-Reply-To: <000c01c13113$91d7c060$0400000a@gorilla> <999159394.23678.285.camel@pc-16.office.scali.no>
In-Reply-To: <999159394.23678.285.camel@pc-16.office.scali.no>
On Aug 30, 2001 10:16 +0200, Terje Eggestad wrote:
> THere is a CLONE_THREAD flag to clone() that sets up a linked list thru
> all the procs (shared VM or not) that in 2.4.3 that I currently run
> don't seem to be ready for general use, managed to get this:
> te 31504 31504 0 10:03 pts/0 00:00:00 [clone2 <defunct>]
> te 31505 31504 0 10:03 pts/0 00:00:00 [clone2 <defunct>]
>
> Where a zombie is waiting for the parent to receive it's SIGCHLD, but
> it's its own parent. Kinda cute, guess Its time to reboot....
I'm pretty sure Linus had a patch for this in 2.4.7 or so, which
reparented the thread to init, so it would be reaped on exit.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
prev parent reply other threads:[~2001-08-30 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 5:21 Multithreaded core dumps Elan Feingold
2001-08-30 5:50 ` Kip Macy
2001-08-30 8:24 ` Alan Cox
2001-08-30 9:03 ` Alexander Viro
2001-08-30 9:12 ` Alan Cox
2001-08-30 10:08 ` Alexander Viro
2001-08-30 9:33 ` David S. Miller
2001-08-30 8:16 ` Multithreaded core dumps (CLONE_THREAD and elf) Terje Eggestad
2001-08-30 9:19 ` Andreas Dilger [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=20010830031918.H541@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=efeingold@mn.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=terje.eggestad@scali.no \
/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).