Messages in this thread | | | Date | Thu, 06 May 1999 23:20:18 -0500 | From | Nicholas Henke <> | Subject | Re: Oops assist... |
| |
Manfred Spraul wrote: > > "Michael B. Trausch" wrote: > > Currently, oops reports are syslog'd. > > Yes, but that's dangerous, because it means that the oops is send > to a user mode process, the user mode process calls write(), fsync(), > etc. > It means that a crashing kernel continues to write to you harddisk. > You want to minimize this as much as possible. > > And: if we deserialize the filesystem, this will often fail, > because the 'kill thread' might cause a lost semaphore, and thus > a deadlock. > > Regards, > Manfred > > - > 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/ What if this were done to a "who-cares" filesystem, such as that on a floppy disk. The user wou;d have to know that the chance for corruption was there, but at least there is a chance thatthere will be some very usefull info Nic -- Nicholas Henke University of Pennsylvania Class of 2002 215-417-5665 (ht/ft)tp://bs28-222-095.resnet.upenn.edu ========================================= Never put off till tomorrow what you can avoid all together.
- 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/
| |