OK, I'll bite. How do you plan to write to a disk partition after an
Oops that has hung the machine? The hang can be caused by interrupts
being disabled, by a lock deadlock, by bottom halves unable to run and
probably some other causes as well. IMHO, any attempt to write Oops to
disk must be done outside the normal kernel I/O mechanisms. If your
I/O uses any interrupts, gets any locks or does any bh processing,
expect your dump to hang as well.
Safely writing an Oops is all very well but any new mechanism needs to
be reliable as well. The more I look at this problem, the more I think
that the only reliable option on a single machine is one that stores
the Oops text in memory that does not get overwritten on reboot.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/