From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: Regression in suspend to ram in 2.6.31-rc kernels Date: Sat, 12 Sep 2009 00:36:41 +0200 Message-ID: <200909120036.41725.rjw@sisk.pl> References: <20090903232317.GA6760@lst.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:46304 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757131AbZIKWfd (ORCPT ); Fri, 11 Sep 2009 18:35:33 -0400 In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Chris Ball Cc: Zdenek Kabelac , Pavel Machek , OGAWA Hirofumi , Christoph Hellwig , Linux Kernel Mailing List , linux-mmc@vger.kernel.org, viro@zeniv.linux.org.uk On Saturday 12 September 2009, Chris Ball wrote: > Hi, > > > Well system could check basic card ids if they match after resume > > No. That (arguably) guarantees that it's the same card, but not that > it wasn't modified in another machine during the suspend. Generally speaking, we'd also need to check superblocks for this to work. > > if some users wants to crash his card by randomly swapping it > > during suspend/resume - I'd have no problem with that.... > > You should have a problem with it. Taking a card from a suspended > machine and working on it with a different machine is not a bizarre > thing to want to do. Agreed. Thanks, Rafael