linux-kernel - Re: USB: on suspend to ram/disk all usb devices are replugged

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070402193606.GA3576@elf.ucw.cz>
Date:	Mon, 2 Apr 2007 21:36:06 +0200
From:	Pavel Machek <pavel@....cz>
To:	Chuck Ebbert <cebbert@...hat.com>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	David Zeuthen <davidz@...hat.com>,
	Maxim <maximlevitsky@...il.com>,
	Pete Zaitcev <zaitcev@...hat.com>, gregkh@...e.de,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: USB: on suspend to ram/disk all usb devices are replugged

Hi!

> > But you're still likely to run into trouble if you unplug a storage
> > device, move it to another system and write on it, then plug it back into
> > the original system.  The PLVM would somehow have to recognize that the
> > data had been changed.  I don't know a foolproof way of doing that.
> > 
> 
> Mark the filesystem as in-use with a one-time UUID in the superblock at
> mount time. If one moved the drive to another system it would require
> an fsck to clear the UUID before the other system could use it; then
> the original machine would refuse to use the drive when the UUID didn't
> match on resume.

You still need fs-specific code, I'm afraid... plus userland tool
to reset signatures back.

Patches welcome. 
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/