From: "Thaddeus H. Black" <thb@debian.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v3] filename.7: new manual page
Date: Thu, 21 Oct 2021 12:18:59 +0000 [thread overview]
Message-ID: <YXFas4WVwuROIDh+@b-tk.org> (raw)
In-Reply-To: <87lf2oxgh9.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]
This long email asks for no one's close attention but Florian's. Other
readers can skim the email or skip it, at their discretion.
On Wed, Oct 20, 2021 at 10:12:02AM +0200, Florian Weimer wrote:
> > > What does this mean? I think only byte 0x2f is reserved. The UTF-8
> > > comment is misleading. A historic/overlong encoding of / in multiple
> > > UTF-8 bytes is *not* reserved.
> >
> > I had not known that UTF-8 had an alternate encoding for any ASCII
> > character. Does it indeed have an alternate encoding? If so, where
> > can I learn more?
>
> See the Security Considerations section in the RFC:
>
> <https://datatracker.ietf.org/doc/html/rfc3629#section-10>
>
> Most file systems do not treat file names as UTF-8, so they do not
> perform any validation.
I see. That RFC explains it well: there exists no legal alternate
encoding, but rather several illegal encodings that, were they not
illegal, *would be* alternate encodings. In the case of the solidus,
the legal encoding is 2F but the illegal encodings are
C0 AF
E0 80 AF
F0 80 80 AF
F8 80 80 80 AF
FC 80 80 80 80 AF
This problem has nothing to do with Unicode but is merely an artifact
of UTF-8 -- and that's your point, isn't it? Most filesystems do not
care about UTF-8, so they do not perform any validation.
In view of your advice, I should think about how to rewrite the relevant
prose so that it is neither [i] confusing to inexperienced users
nor [ii] inaccurate.
Question: the filename(7) manual page ought to emphasize the
requirements of filesystems widely deployed for general-purpose use on
standard Linux installations. As far as I know, exactly three such
filesystems exist:
* ext4;
* xfs;
* btrfs.
Do any other such filesystems exist?
Comments:
1. I have heard of reiserfs and reiser4 but have not heard of anyone
that actually uses them since about 15 years ago.
2. There are also nfs, iso9660/joliet/rockridge, vfat, ntfs, cifs
and a few others. These are network-oriented, archive-oriented,
special-purpose, foreign and/or compatibility-oriented filesystems. If
the filename(7) manual page mentions the requirements of such
filesystems at all, it should mention them only briefly, in passing.
Otherwise, the page would become too confusing and grow too long.
(Also, I know too little about most of these extra filesystems to write
about them.)
3. Happily, the three main filesystems -- ext4, xfs and btrfs -- all
have similar filename requirements as far as I know.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-21 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 23:07 [PATCH v2] filename.7: new manual page Thaddeus H. Black
2021-10-18 16:25 ` Thaddeus H. Black
2021-10-18 16:33 ` [PATCH v3] " Thaddeus H. Black
2021-10-19 8:54 ` Florian Weimer
2021-10-19 11:05 ` Thaddeus H. Black
2021-10-19 13:55 ` Alejandro Colomar (man-pages)
2021-10-20 8:12 ` Florian Weimer
2021-10-21 12:18 ` Thaddeus H. Black [this message]
2021-10-19 13:38 ` Alejandro Colomar (man-pages)
2021-11-07 14:36 ` Thaddeus H. Black
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=YXFas4WVwuROIDh+@b-tk.org \
--to=thb@debian.org \
--cc=alx.manpages@gmail.com \
--cc=fweimer@redhat.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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