From: Shreeya Patel <shreeya.patel@collabora.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
krisman@collabora.com, preichl@redhat.com, kernel@collabora.com
Subject: Re: [PATCH] generic/453: Exclude filenames that are not supported by exfat
Date: Mon, 26 Apr 2021 17:27:51 +0530 [thread overview]
Message-ID: <a49ecbfb-2011-0c7c-4405-b4548d22389d@collabora.com> (raw)
In-Reply-To: <20210426003430.GH235567@casper.infradead.org>
On 26/04/21 6:04 am, Matthew Wilcox wrote:
> On Mon, Apr 26, 2021 at 04:01:05AM +0530, Shreeya Patel wrote:
>> exFAT filesystem does not support the following character codes
>> 0x0000 - 0x001F ( Control Codes ), /, ?, :, ", \, *, <, |, >
> ummm ...
>
>> -# Fake slash?
>> -setf "urk\xc0\xafmoo" "FAKESLASH"
> That doesn't use any of the explained banned characters. It uses 0xc0,
> 0xaf.
>
> Now, in utf-8, that's an nonconforming sequence. "The Unicode and UCS
> standards require that producers of UTF-8 shall use the shortest form
> possible, for example, producing a two-byte sequence with first byte 0xc0
> is nonconforming. Unicode 3.1 has added the requirement that conforming
> programs must not accept non-shortest forms in their input."
>
> So is it that exfat is rejecting nonconforming sequences? Or is it
> converting the nonconforming sequence from 0xc0 0xaf to the conforming
> sequence 0x2f, and then rejecting it (because it's '/')?
>
No, I don't think exfat is not converting nonconforming sequence from
0xc0 0xaf
to the conforming sequence 0x2f.
Because I get different outputs when tried with both ways.
When I create a file with "urk\xc0\xafmoo", I get output as "Operation
not permitted"
and when I create it as "urk\x2fmoo", it gives "No such file or
directory error" or
you can consider this error as "Invalid argument"
( because that's what I get when I try for other characters like |, :,
?, etc )
Box filename also fails with "Invalid argument" error.
next prev parent reply other threads:[~2021-04-26 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 22:31 [PATCH] generic/453: Exclude filenames that are not supported by exfat Shreeya Patel
2021-04-26 0:34 ` Matthew Wilcox
2021-04-26 11:57 ` Shreeya Patel [this message]
2021-04-26 12:03 ` Shreeya Patel
2021-04-26 12:37 ` Matthew Wilcox
2021-04-27 11:13 ` Shreeya Patel
2021-04-27 18:11 ` Darrick J. Wong
2021-04-27 21:00 ` Shreeya Patel
2021-04-28 13:50 ` Theodore Ts'o
2021-04-29 0:37 ` Darrick J. Wong
2021-04-29 14:32 ` Gabriel Krisman Bertazi
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=a49ecbfb-2011-0c7c-4405-b4548d22389d@collabora.com \
--to=shreeya.patel@collabora.com \
--cc=fstests@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=preichl@redhat.com \
--cc=willy@infradead.org \
/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).