mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: cw@f00f.org (Chris Wedgwood)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	n0ano@valinux.com (Don Dugger),
	linux-kernel@vger.kernel.org
Subject: Re: Core dumps for threads
Date: Sun, 25 Feb 2001 13:57:31 +0000 (GMT)	[thread overview]
Message-ID: <E14X1g5-00033i-00@the-village.bc.nu> (raw)
In-Reply-To: <20010225221505.A12595@metastasis.f00f.org> from "Chris Wedgwood" at Feb 25, 2001 10:15:05 PM

> On Sat, Feb 24, 2001 at 09:57:44PM +0000, Alan Cox wrote:
> 
>     The I/O to dump the core would race other changes on the mm. The
>     right fix is probably to copy the mm (as fork does) then dump the
>     copy.
> 
> Stupid question... but since all threads see the same memory space as
> each other; can we not lock the entire vma for the process whilst
> it's being written out?

It isnt the vma, its the entire mm you would need to lock. And I dont think
you can do a deadlock free lock of that sanely, hence its better to copy
the mm (thats pretty efficienty anyway as it wont copy the data)


  parent reply	other threads:[~2001-02-25 13:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-24 21:45 Don Dugger
2001-02-24 21:57 ` Alan Cox
2001-02-25  9:15   ` Chris Wedgwood
2001-02-25  9:40     ` Adam Fritzler
2001-02-26  0:36       ` davids
2001-02-25 10:28     ` Andi Kleen
2001-02-25 11:03       ` Chris Wedgwood
2001-02-25 13:57     ` Alan Cox [this message]
2001-02-27 17:29   ` [PATCH] " Don Dugger
2001-02-27 17:55     ` Alan Cox
2001-02-27 17:57     ` 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=E14X1g5-00033i-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n0ano@valinux.com \
    /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

all inboxes | Powered by JetHome®