Date: Sun, 17 Apr 2005 09:09:07 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: David Schultz <das@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/fs/msdosfs msdosfs_lookup.c Message-ID: <1404.1113721747@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 16 Apr 2005 23:47:19 -0000." <200504162347.j3GNlJUA010418@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200504162347.j3GNlJUA010418@repoman.freebsd.org>, David Schultz wri tes: > Log: > Disable negative name caching for msdosfs to work around a bug. > Since the name cache is case-sensitive and msdosfs isn't, > creating a file 'foo' won't invalidate a negative entry for 'FOO'. > There are similar problems related to 8.3 filenames. > > A better solution is to override VOP_LOOKUP with a method that > canonicalizes the name, then calls vfs_cache_lookup(). Unfortunately, > it's not quite that simple because vfs_cache_lookup() will call > msdosfs_lookup() on a cache miss, and msdosfs_lookup() needs a way to > get at the original component name. I thought about something like that many years ago when I had copied a file called read:me to a msdosfs floppy and handed it to a NT using coworker who spent most of the day figuring out why he couldn't get the damn file off the floppy. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1404.1113721747>