> One thought: The main objection to the idea of dumpiing to disk has been
> in connection with the fact that at the time the dump is needed, it might
> not be possible to get reliable details as to where to put it on the
> disk.
The classic answer is using the swapspace for the dump from where a savecore
program will copy the coredump to /var/adm/crash/ and eventually do some
analysis and further processing of the dump.
> To me, the obvious answer to that is to have the dump driver hold a local
> pointer to the relevant location, initialise it at system boot, and have
> hooks in the mount and sync routines to ensure it's still valid.
A more interesting issue is how you'll handle the state of all the kernel
locks.
Ralf
-
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/