Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> writes: > On Mon, 9 Jul 2007, Jeremy Maitin-Shepard wrote: >> Pavel Machek <pavel@xxxxxx> writes: >> >> [snip] >> >> > I don't know how to do that mechanism... but if we knew where to trap >> > filesystem writes, we could simply freeze at that point, and at that >> > point only, no? >> >> Any operation at all that has an external effect must not occur after >> the snapshot is made; otherwise, there will be random hard-to-find >> corruptions and other problems occurring as a result. Thus, for >> example, any writes (either directly or indirectly through e.g. a >> filesystem) to non-volatile storage, any network traffic, any >> communication with hardware like a printer must be prevented after the >> snapshot. > You have forgotten one critical point: The writes to save the snapshot > image must be allowed. That's what makes it really hard. Well, I didn't forget about that, although my language may have been a bit ambiguous. I was referring only to the operations that are done by normal (i.e. non-hibernate) portions of the system and which are not explicitly for the purpose of hibernating the system. It is very difficult to maintain this guarantee while also attempting to reuse the same infrastructure that is supposed to not be processing any "normal" requests in order to write the snapshot. The kdump approach handily avoids this problem by *not* reusing the same infrastructure while still allowing complete flexibility (i.e. not depending on a drivers/suspend/ide-simple). -- Jeremy Maitin-Shepard _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
