From: Calvin Walton <calvin.walton@kepstin.ca>
To: Marian Beermann <public@enkore.de>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [BUG] NTFS code doesn't sanitize folder names sufficiently
Date: Fri, 27 Jul 2012 10:28:55 -0400 [thread overview]
Message-ID: <1343399335.7767.6.camel@cwalton-XPS-8300> (raw)
In-Reply-To: <501189DA.4030709@enkore.de>
On Thu, 2012-07-26 at 20:18 +0200, Marian Beermann wrote:
> Hello everyone,
>
> today I noticed some very odd behaviour, which could lead people to
> believe a loss of data, because it is possible to create directories
> with backslashes in them.
>
> I am currently running kernel 3.5.
>
> To completly reproduce the problem to the full extend you'll need a
> Windows computer, but to see whats wrong Linux completly suffices :-)
>
> On a Linux computer
> 1. Create a directory named TestA on an NTFS partition
> 2. Create a subdirectory of TestA named TestB
> 3. Create a third directory alongside TestA named TestA\TestB (the
> fundamental problem is this: backslashes in directory names)
If you're writing new directories to an NTFS partition, it's very
probable that you're not actually using the in-kernel NTFS driver at
all. It's more likely that you have the userspace (FUSE) NTFS driver
instead:
http://www.tuxera.com/community/ntfs-3g-download/
In fact, they have a FAQ about it the issue that you're seeing:
http://www.tuxera.com/community/ntfs-3g-faq/#posixfilenames2
You use the 'windows_names' mount option to disable creating file and
directory names that confuse windows.
Linux itself (and most native Linux programs) has no issues with
directory names containing the '\' character, of course; the only
characters that you cannot use are '/' and ASCII NUL, 0x00.
--
Calvin Walton <calvin.walton@kepstin.ca>
next prev parent reply other threads:[~2012-07-27 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 18:18 [BUG] NTFS code doesn't sanitize folder names sufficiently Marian Beermann
2012-07-27 14:28 ` Calvin Walton [this message]
2012-08-01 23:16 ` Cody P Schafer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1343399335.7767.6.camel@cwalton-XPS-8300 \
--to=calvin.walton@kepstin.ca \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=public@enkore.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).