David Chinner wrote: > On Thu, Apr 03, 2008 at 01:14:50PM -0400, Christoph Hellwig wrote: > > Validating file names is not the filesystem job. In fact it's utterly > > stupid, a unix filename is a sequence of bytes without special meaning > > except for ., .., / and \0 > > So you're suggesting that we should rely on userspace being bug free > and always only using valid unicode sequences in it's names? You can bet that one person's "invalid unicode sequence" will have been used as a valid filename on someone else's filesystem even using unicode. Meanings of "invalid unicode sequence" vary (a lot) depending on which standard you follow. Annoyance will come when they try to copy the directory. Such things are no great surprise on Windows and MacOS (both of which do even worse things than rejecting sequences), but in POSIX land we expect things like that to work. The rules for ., .., / and \0, and accepting the rest as a blob, have been well defined and understood for a long time. -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
