Messages in this thread | | | Date | Fri, 23 Apr 2004 14:56:50 +0200 | From | Pavel Machek <> | Subject | Re: SOFTWARE_SUSPEND as a module |
| |
Hi!
> > If you really ensure userspace is stopped, you should be fine. > > > > *But* kernel is only correct if userspace is "correct", and need for > > all processes stopped is not going to be obvious to users. I'd like > > kernel to be kernel to be okay regardless what stupid stuff happens in > > userspace. (Well, they really should not scribble on disks). > > But in this context if user space is not doing the right thing, > you'll lose whatever the kernel does. For example, if user space > writes to any file systems mounted in the suspended image, then > you'll get corruption no matter what the kernel does.
Hmm, this should keep users from doing so. Alternative solution is to add your own warning ;-).
Pavel
* BIG FAT WARNING ********************************************************* * * If you touch anything on disk between suspend and resume... * ...kiss your data goodbye. *
-- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |