fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: Viacheslav Dubeyko <slava@dubeyko.com>,
	zlang@redhat.com, fstests@vger.kernel.org,
	glaubitz@physik.fu-berlin.de, vdubeyko@coreweave.com,
	linux-fsdevel@vger.kernel.org, frank.li@vivo.com
Subject: Re: [PATCH] xfstests: exclude hfs/hfsplus from generic/339 run
Date: Thu, 10 Sep 2026 09:49:28 -0400	[thread overview]
Message-ID: <aqKzDpccJgkmzC5E@mit.edu> (raw)
In-Reply-To: <aqJ--AqubS-CWiV-@infradead.org>

On Thu, Sep 10, 2026 at 02:57:12AM -0500, Christoph Hellwig wrote:
> On Wed, Sep 09, 2026 at 05:04:50PM -0700, Viacheslav Dubeyko wrote:
> > The dirhash_collide generates filenames from arbitrary random
> > bytes (only '.' and '/' are filtered out), which are not valid
> > UTF-8 in general. Catalog names on both classic HFS and HFS+ are
> > Unicode. Feeding random bytes causes fsck to report "Illegal name"
> > or catalog corruption that has nothing to do with directory
> > hash-collision handling, which is what this test is actually meant
> > to exercise.

I'm curious --- does HFS/HFS+ reject unofficial Unicode characters
such as those used by Klingon?  (Klingon is an invented/artificial
language, so it's considered out of scope by Unicode; so Star Trek
enthusiasts are camping on an unofficial block of the Unicode code
set.)

Invalid Unicode characters could also happen because newer versions
of Unicode have added new emoji's, which might be added as support in
the mobile handset userspace, but since we aren't regularly updating
the Unicode tables, they might still be considered invalid if you
enable strict mode in ext4/f2fs.

> If user file name creation manage to trigger fsck complaints, you need
> to righten the input checks in the file systems first to fix this.
> 
> We can then find a programmatic way to deal with these rejects in
> xfstests, as ext4/f2fs in case insensiive mode probably have the same
> issue.

Well, strict mode isn't enabled by default, since users might want to
use Klingon or emoji's with a skin color that matches their own.  And
no one has been invested enough to continuously update our Unicode
tables, and add support in the userspace tooling for upgrading the
Unicode version in the file system superblock (which would then break
compatibility with older kernels --- for example, if they downgrade to
an older version of Android, etc.)

Isn't Unicode **fun**?  :-)

    	       	       	      	   	      - Ted

  reply	other threads:[~2026-09-10 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  0:04 [PATCH] xfstests: exclude hfs/hfsplus from generic/339 run Viacheslav Dubeyko
2026-09-10  9:57 ` Christoph Hellwig
2026-09-10 13:49   ` Theodore Tso [this message]
2026-09-10 21:14     ` Viacheslav Dubeyko
2026-09-11 14:48       ` Theodore Tso
2026-09-14 18:45         ` Viacheslav Dubeyko
2026-09-10 20:13   ` Viacheslav Dubeyko
2026-09-11  7:09     ` Christoph Hellwig
2026-09-14 18:19       ` Viacheslav Dubeyko

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=aqKzDpccJgkmzC5E@mit.edu \
    --to=tytso@mit.edu \
    --cc=frank.li@vivo.com \
    --cc=fstests@vger.kernel.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=slava@dubeyko.com \
    --cc=vdubeyko@coreweave.com \
    --cc=zlang@redhat.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;
as well as URLs for NNTP newsgroup(s).