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. Ralf -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>