The solution to this would be to disallow creation of files and
folders on NTFS drives containing illegal characters.
Illegal characters with respect to Windows & the like are different
from Illegal characters with respect to the NTFS filesystem structure.
Looking at ntfs-3g(8) [yes, I'm aware that is a different driver that
this bug is about], the section on Windows Filename Compatability says
this:
[...] all characters are
allowed except '/' and '\0'. This is perfectly legal on Windows,
though some application may get
confused. The option windows_names may be used to apply Windows
restrictions to new file names.
To recap: no data will be lost due to using '\' in filenames. Some
operating systems just may not be capable off accessing it.
--
Cody
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
