Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751962AbXE2Vf0 (ORCPT ); Tue, 29 May 2007 17:35:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750815AbXE2VfP (ORCPT ); Tue, 29 May 2007 17:35:15 -0400 Received: from smtp1.linux-foundation.org ([207.189.120.13]:55691 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750722AbXE2VfN (ORCPT ); Tue, 29 May 2007 17:35:13 -0400 Date: Tue, 29 May 2007 14:33:37 -0700 (PDT) From: Linus Torvalds To: Nigel Cunningham cc: Mark Lord , Pavel Machek , Romano Giannetti , Chris Wright , Chuck Ebbert , Linux Kernel Mailing List , stable@kernel.org, Justin Forbes , Zwane Mwaikambo , "Theodore Ts'o" , Randy Dunlap , Dave Jones , Chuck Wolber , Chris Wedgwood , Michael Krufky , akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk, "Rafael J. Wysocki" Subject: Re: pcmcia resume 60 second hang. Re: [patch 00/69] -stable review In-Reply-To: <1180473765.20718.47.camel@nigel.suspend2.net> Message-ID: References: <1179870110.16656.2.camel@localhost> <1180008394.15600.26.camel@localhost> <20070524200435.GA9604@elf.ucw.cz> <20070524220017.GC9604@elf.ucw.cz> <20070524221743.GD9604@elf.ucw.cz> <20070524231852.GG9604@elf.ucw.cz> <1180058123.3997.91.camel@nigel.suspend2.net> <1180059605.3997.100.camel@nigel.suspend2.net> <1180062040.3997.112.camel@nigel.suspend2.net> <1180067587.3997.136.camel@nigel.suspend2.net> <465C366C.2070900@rtr.ca> <1180473765.20718.47.camel@nigel.suspend2.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1340 Lines: 31 On Wed, 30 May 2007, Nigel Cunningham wrote: > > On Tue, 2007-05-29 at 10:19 -0400, Mark Lord wrote: > > > > How about blocking brk() and mmap(MAP_ANONYMOUS) in addition to > > the filesystem VFS callers? Or is that starting to get messy again? > > Yeah. Getting messy again :) Indeed. And also misses the point - the point being that we don't actually need to freeze anything at all most of the time. There's nothing wrong with making memory allocations etc. And yes, suspend is different from hibernate. I can see how hibernate people are worried about people writing to things after doing the snapshot, but those concerns don't exist with suspend. With suspend, the biggest concern is accessing a device after it has been suspended, but on the other hand, also the fact that we end up having driver writers used to the system being "runnable", so they do things that really do require a full-fledged system (and sometimes that means just some delayed action using a kernel thread, other times it seems to rely on more complex behaviour like firmware loading :^p ) Linus - 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/