In some email I received from Brett Lymn, sie wrote:
[...]
> Actually, in a lot of the cases panics are about the only thing you
> can do.  What sort of handling do you want to do when the file system
> finds the inode it is trying to free is already free?  Just say "gee
> I musta lost the plot there someplace, I will just continue on..." to
> do more damage to the file system.  How do you handle a hard error in
> your swap space?  Just kill the process and continue on?  What if the
> process is inetd?  or even init?

I'm sure I've seen this behaviour with swap space and processes being
killed in commercial Unixes...