[Top] [All Lists]

Re: Issue with core dump

To: Oleg Nesterov <>
Subject: Re: Issue with core dump
From: Tejun Heo <>
Date: Tue, 1 Nov 2011 08:59:45 -0700
Cc: trisha yad <>, linux-mm <>, Russell King - ARM Linux <>,,,,,, Andrew Morton <>, Konstantin Khlebnikov <>, KOSAKI Motohiro <>, "Rafael J. Wysocki" <>, Rusty Russell <>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=niMISTMFnh5R4oEAU5DX47GEf+r8XSa/lL3yalhTxtQ=; b=u0Ly0DQZohCzoFNid1UHfHcjYoP9R1dfKTyac4Ud0BuSCfRk66nH1H1LSYppTgEd05 UObGiXrYO9+f8FK9Xk7NCYtVhOP20ddBWaeIbKOQZ+/Z5Cpxd2Vi4eUDLJ0pknc84cAu hG+8IbZTeldOB4p4HDfglxGmm1ILgUhNSvZm0=
In-reply-to: <>
References: <> <>
User-agent: Mutt/1.5.20 (2009-06-14)

On Tue, Nov 01, 2011 at 04:23:20PM +0100, Oleg Nesterov wrote:
> Whatever we do, we can't "stop" other threads at the time when
> thread 'a' traps. All we can do is to try to shrink the window.

Yeah, "at the time" can't even be defined preciesly.  Order of
operation isn't clearly defined in absence of synchronization
constructs.  In the described example, there's unspecified amount of
time (or cycles rather) between the load of the global variable and
the thread faulting.  Anything could have happened inbetween no matter
how immediate core dump was.

As long as we're reasonably immediate, which I think we already are, I
don't think there's much which needs to be changed.



<Prev in Thread] Current Thread [Next in Thread>