public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Robert Love <rml@tech9.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	MAEDA Naoaki <maeda.naoaki@jp.fujitsu.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PID of multi-threaded core's file name is wrong in 2.5.59
Date: Tue, 28 Jan 2003 12:39:49 -0500	[thread overview]
Message-ID: <20030128173949.GA23077@nevyn.them.org> (raw)
In-Reply-To: <1043774823.9069.59.camel@phantasy>

On Tue, Jan 28, 2003 at 12:27:03PM -0500, Robert Love wrote:
> On Tue, 2003-01-28 at 10:45, Daniel Jacobowitz wrote:
> 
> > I think this isn't an issue; multi-threaded core dumps are done by
> > the core_waiter synchronization, so all other threads will have exited
> > before the first thread to crash actually writes out its core.
> 
> I think the problem is the filenames need to not overwrite each other -
> not actual synchronization in the kernel (which, as you point out, is
> correct).
> 
> If we name the coredumps based on ->tgid, then all threads will dump to
> the same file.  If we use ->pid, each thread will use its unique PID as
> its filename.

That wasn't my point.  All of the other threads have already terminated
without dumping core at tis point; I don't think it's possible for two
threads of a CLONE_THREAD application to both dump core.  See
fs/exec.c:coredump_wait.

Also, once one thread gets into do_coredump it clears mm->dumpable;
nothing else will dump core from that MM anyway.

I think using ->tgid is a good idea.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-01-28 17:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-25  4:56 PID of multi-threaded core's file name is wrong in 2.5.59 MAEDA Naoaki
2003-01-28 12:21 ` Alan Cox
2003-01-28 15:45   ` Daniel Jacobowitz
2003-01-28 17:27     ` Robert Love
2003-01-28 17:39       ` Daniel Jacobowitz [this message]
2003-01-28 17:42         ` Robert Love
2003-01-28 17:49           ` Daniel Jacobowitz
2003-01-28 18:49             ` 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=20030128173949.GA23077@nevyn.them.org \
    --to=dan@debian.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maeda.naoaki@jp.fujitsu.com \
    --cc=rml@tech9.net \
    /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