> > while the dump is taken? How about thread A coredumping, half of the image
> > being already written and thread B (nowhere near the kernel mode, mind
> > you) changing the data both in the area that is already dumped and area
> > the still isn't? After that you can look at the dump and notice absolutely
> > corrupted data structures - very effective in misdirecting your attempts
> > to figure out what went wrong.
>
> Couldn't all threads be stopped before coredumping begins?
Unless I am missing something doesn't a truncate of a file in parallel also
yank the pages from under the dump too
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Sep 30 2000 - 21:00:25 EST