Date: Fri, 17 Feb 2006 22:04:45 +0100
From: Pavel Machek <pavel@suse.cz>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Alan Stern <stern@rowland.harvard.edu>, Kyle Moffett <mrmacman_g4@mac.com>,
       Alon Bar-Lev <alon.barlev@gmail.com>,
       Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Flames over -- Re: Which is simpler?
Message-ID: <20060217210445.GR3490@openzaurus.ucw.cz>
References: <Pine.LNX.4.44L0.0602131601220.4754-100000@iolanthe.rowland.org> <43F11A9D.5010301@cfl.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43F11A9D.5010301@cfl.rr.com>
User-Agent: Mutt/1.3.27i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1314
Lines: 33

Hi!


> >You are ignoring the question of how the kernel can tell whether two 
> >devices are in fact the same.  There is no safe way to do this, 
> >other than having the hardware verify that the device was connected 
> >the whole time.
> >
> >  
> If there is no better way to tell for sure that the device that is 
> now there is not the same as the one that was there, then the kernel 
> must assume the user did not do something stupid and continue to use 

Must?! Are you Linus or what?

> the device as if it was not disconnected ( because odds are, it in 
> fact, was not ).  In other words, which is more safe?  ALLWAYS 
> loosing data because you can't be absolutely sure that the device is 
> the same, or only loosing data if the user does something as foolish 
> as swapping drives while suspended, and you can't tell they did?

You are missing this. In 1st case, no data is actually lost, because of
sync in suspend code;
while second case is "goodbye, filesystem".
				Pavel
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         

-
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/