From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Re: [PATCH] Remove process freezer from suspend to RAM pathway Date: Fri, 06 Jul 2007 08:38:15 +1000 Message-ID: <1183675095.3388.72.camel@localhost.localdomain> References: <18059.10554.955290.148535@cargo.ozlabs.ibm.com> <200707051024.23528.oliver@neukum.org> <200707051048.46202.oliver@neukum.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200707051048.46202.oliver@neukum.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Oliver Neukum Cc: mjg59@srcf.ucam.org, Miklos Szeredi , linux-kernel@vger.kernel.org, pavel@ucw.cz, johannes@sipsolutions.net, linux-pm@lists.linux-foundation.org List-Id: linux-pm@vger.kernel.org > There is that. > > OK, bite the bullet. Tasks involved in fuse are special. Give them a flag > and teach the freezer to put them on ice only after all other task are > frozen. In a way they are kernel, there's no use denying that. Yet another ugly hack to work around the fact that the freezer cannot work reliably ... yuck Why not spend that energy fixing drivers to properly block requests instead ? Ben.