Messages in this thread | | | From | Oleg Verych <> | Subject | Off topically about Re: malicious filesystems (was Re: Re: [PATCH] Remove process freezer from suspend to RAM pathway) | Date | Sun, 8 Jul 2007 08:15:31 +0000 (UTC) |
| |
>> > > We can just wait for all fuse requests to be serviced before >> > > proceeding further with freeze, right? >> > >> > Right. Nice way to slow down or stop the suspend with an unprivileged >> > process. Avoiding that sort of DoS is one of the design goals of >> > fuse. >> >> So you want me to handle _malicious_ filesystems now? > > What I'd like, is a suspend, that works reliably, regardless of the > state of any userspace filesystem, network servers and such.
And this must be called sleep, deep sleep or something like that. Because preparing for sleeping takes place, sleeping itself is a process, life requires. Waking up, staying all day fresh and active is the needed goal.
Thus, whole freeze/ice idea was dead-born, IMHO :)
WRT this, busy-loop _waiting_ that was called sleep, usleep or nanosleep is another wrong-named concept. I imagine somebody after one minute sleep :) ____
- 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/
| |