Message-ID: <5019B8B1.7090902@linux.vnet.ibm.com>
Date: Wed, 01 Aug 2012 16:16:01 -0700
From: Cody P Schafer <cody@linux.vnet.ibm.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Marian Beermann <public@enkore.de>
CC: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] NTFS code doesn't sanitize folder names sufficiently
References: <501189DA.4030709@enkore.de>
In-Reply-To: <501189DA.4030709@enkore.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1040
Lines: 28


> 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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/