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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080527114146.GB16868@elf.ucw.cz>
Date:	Tue, 27 May 2008 13:41:46 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Theodore Tso <tytso@....edu>, Ingo Molnar <mingo@...e.hu>,
	Jan Kara <jack@...e.cz>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Top 10 bugs/warnings for the week of March 23rd, 2008

On Mon 2008-05-26 19:09:57, Oliver Neukum wrote:
> Am Montag 26 Mai 2008 19:01:48 schrieb Theodore Tso:
> > If the USB stack folks would like to work on how to recognize that
> > it's the same USB stick that had been previously pulled, so that it
> > gets the same block device, and we can decide for how long we should
> > keep dirty buffers around associated with a pulled USB stick, we can
> > certainly have that conversation.  :-)
> 
> Even if we could tell whether the device has remained the same, how
> would we know the medium wasn't exchanged?

We need filesystem support for that, but I guess we should just bite
the bullet and do it for the most common filesystems... it is very
useful for suspend/resume, too and I have heared about (misdesigned)
machines where it will be basically mandatory...
								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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ