[Top] [All Lists]

Re: Issue with core dump

To: trisha yad <>
Subject: Re: Issue with core dump
From: Ralf Baechle <>
Date: Wed, 2 Nov 2011 11:30:31 +0000
Cc: Oleg Nesterov <>, linux-mm <>, Russell King - ARM Linux <>,,,,,, Andrew Morton <>, Konstantin Khlebnikov <>, KOSAKI Motohiro <>, "Rafael J. Wysocki" <>, Rusty Russell <>, Tejun Heo <>
In-reply-to: <>
References: <> <> <>
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Nov 02, 2011 at 12:03:39PM +0530, trisha yad wrote:

> Thanks all for your answer.
> In loaded embedded system the time at with code hit do_user_fault()
> and core_dump_wait() is bit
> high, I check on my  system it took 2.7 sec. so it is very much
> possible that core dump is not correct.
> It  contain global value updated.
> So is it possible at time of send_signal() we can stop modification of
> faulty thread memory ?

On existing hardware it is impossible to take a consistent snapshot of a
multi-threaded application at the time of one thread faulting.

A software simulator can handle this sort of race condition but of course
this approach has other disadvantages.


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