[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1I5no4-0004fU-00@dorka.pomaz.szeredi.hu>
Date: Tue, 03 Jul 2007 21:13:00 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: oliver@...kum.org
CC: rjw@...k.pl, benh@...nel.crashing.org, mjg59@...f.ucam.org,
linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
pavel@....cz, nigel@...el.suspend2.net
Subject: Re: [PATCH] Remove process freezer from suspend to RAM pathway
> And a further question. The freezer is not atomic. What do you do
> if a task not yet frozen calls sys_sync(), but fuse is already frozen?
What do you do if a task not yet frozen writes to a pipe, on the other
end of which is a task already frozen?
It doesn't matter. The only thing that should matter during suspend
(not hibernate) is saving the state of devices to ram, and putting the
devices to sleep.
I'm not sure why this can't be made atomic, but assuming, that it
can't, fuse should still not need to be implicated. If it is, that's
an indication about something wrong in the suspend procedure.
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists