[PATCH RFC] vfat and Simon_&_Garfunkel-Wednesday_Morning,_3_a.m.
From: Philippe De Muyter
Date: Fri Sep 25 2009 - 15:46:55 EST
Hello vfat guru's
I have an IOMEGA home network hard disk that I can connect either by
ethernet (ftp or cifs) or by USB. because of the ftp server mode
firmware, I must keep it formatted as a vfat filesystem.
I have copied my music files on it using the ftp mode. Using the same
ftp mode, I can also retrieve my music files without problem, and
when I list them, they have the exact names that they had on my linux
ext3 partition.
When I connected this disk via USB, now relying on the vfat module
of linux, there were some directories that I could not reread. The
common factor of these directories names is that they end with one or
more dots, e.g.
Simon_&_Garfunkel-Wednesday_Morning,_3_a.m.
If I issue the `ls' or `find' command, I get this strange message :
find: ./Simon_&_Garfunkel-Wednesday_Morning,_3_a.m.: No such file or directory
Adding printk's in `fat_search_long' revealed that on this disk, the
file/directory NAMES ENDING WITH DOTS ARE STORED WITH THEIR TRAILING DOTS.
Here is a patch squetch that make accessing my
Simon_&_Garfunkel-Wednesday_Morning,_3_a.m. directory possible, but I
don't know if storing long filenames ending with dot's should not also
be fixed.
Signed-off-by: Philippe De Muyter <phdm@xxxxxxxxx>
diff -r f2c5827a8d44 fs/fat/namei_vfat.c
--- a/fs/fat/namei_vfat.c Mon Aug 31 17:44:05 2009 -1000
+++ b/fs/fat/namei_vfat.c Fri Sep 25 21:30:36 2009 +0200
@@ -702,10 +702,7 @@
static int vfat_find(struct inode *dir, struct qstr *qname,
struct fat_slot_info *sinfo)
{
- unsigned int len = vfat_striptail_len(qname);
- if (len == 0)
- return -ENOENT;
- return fat_search_long(dir, qname->name, len, sinfo);
+ return fat_search_long(dir, qname->name, qname->len, sinfo);
}
static struct dentry *vfat_lookup(struct inode *dir, struct dentry *dentry,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/