linux-ext4 - Re: blkid oddities with stale devices in the cache

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]

Date:	Sun, 6 Jul 2008 14:40:56 -0400
From:	Theodore Tso <tytso@....EDU>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: blkid oddities with stale devices in the cache

On Sat, Jul 05, 2008 at 11:36:09PM -0500, Eric Sandeen wrote:
> Eric Sandeen wrote:
> > This is w.r.t. https://bugzilla.redhat.com/show_bug.cgi?id=452333
> > 
> > Dave had a few stale entries in blkid.tab; label from a usb key showed
> > up under several non-existent, stale device names.  fstab had LABEL=,
> > mounting by label failed because blkid returned a stale, nonexistent device.
> 
> Ted, ping (when you're done kernel-wrangling anyway)?  Any thoughts on
> this?  Returning cached data for a device when stat says ENOENT seems
> very weird (and wrong).

Check out what I just pushed out to the git repository.  I think this
should solve the problems people have been reporting....

       	     	 	  	      	   - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html