From: Dave Chinner <david@fromorbit.com>
To: Olaf Weber <olaf@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, Ben Myers <bpm@sgi.com>,
tinguely@sgi.com, xfs@oss.sgi.com
Subject: Re: [RFC] Unicode/UTF-8 support for XFS
Date: Wed, 17 Sep 2014 06:54:06 +1000 [thread overview]
Message-ID: <20140916205406.GJ4322@dastard> (raw)
In-Reply-To: <54169248.1090105@sgi.com>
On Mon, Sep 15, 2014 at 09:16:24AM +0200, Olaf Weber wrote:
> On 12-09-14 22:55, Christoph Hellwig wrote:
> >On Fri, Sep 12, 2014 at 01:55:35PM +0200, Olaf Weber wrote:
> >>I looked up those discussions in the archives. For example, here's
> >>Christoph about rejecting filenames if they're not well-formed unicode.
> >> http://marc.info/?l=linux-fsdevel&m=120876935526856&w=2
> >>And Jamie Lokier making a similar point:
> >> http://oss.sgi.com/archives/xfs/2008-04/msg01263.html
> >
> >And I might now disagree with my past self. While non-ut8 characters
> >are perfectly valid unix filenames, and I think everyones life is easier
> >if we generally stay out of the utf8 business it seems that for this
> >particular use case (shared filesystem with Windows, right) just
> >accepting utf8 should be fine. ZFS is doing, MacOS X apparently is,
> >and NFSv4 requires it, although as far as I know most implementations
> >ignore that requirement.
> >
>
> One issue is working in environments that are not UTF-8 clean. For
> example, unpacking a tarball with non-UTF-8 filenames in it. The
> names would have to be transcoded, which is only really possible if
> you know the original character set. And if the filesystem flat out
> rejects non-UTF-8 filenames, then you'd be unable to unpack the
> tarball at all.
So how do existing utf8/unicode enabled filesystems handle this?
I think we should be consistent with ZFS, MacOS and others that
already deal with this problem if at all possible. However, this
really is a wider policy decision for the kernel/VFS as we want
consistent behaviour across all linux filesystems, hence this
patchset really needs to discussed at the lkml/-fsdevel level...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-16 20:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 20:37 [RFC] Unicode/UTF-8 support for XFS Ben Myers
2014-09-11 20:40 ` [PATCH 1/9] xfs: return the first match during case-insensitive lookup Ben Myers
2014-09-11 20:41 ` [PATCH 2/9] xfs: rename XFS_CMP_CASE to XFS_CMP_MATCH Ben Myers
2014-09-11 20:42 ` [PATCH 3/9] xfs: add xfs_nameops.normhash Ben Myers
2014-09-11 20:43 ` [PATCH 4/9] xfs: change interface of xfs_nameops.normhash Ben Myers
2014-09-11 20:46 ` [PATCH 5/9] xfs: add a superblock feature bit to indicate UTF-8 support Ben Myers
2014-09-11 20:47 ` [PATCH 6/9] xfs: add unicode character database files Ben Myers
2014-09-11 20:48 ` [PATCH 7/9] xfs: add trie generator and supporting code for UTF-8 Ben Myers
2014-09-11 20:49 ` [PATCH 8/9] xfs: add xfs_nameops for utf8 and utf8+casefold Ben Myers
2014-09-11 20:50 ` [PATCH 9/9] xfs: apply utf-8 normalization rules to user extended attribute names Ben Myers
2014-09-11 20:51 ` [PATCH 01/13] libxfs: return the first match during case-insensitive lookup Ben Myers
2014-09-11 20:52 ` [PATCH 02/13] libxfs: rename XFS_CMP_CASE to XFS_CMP_MATCH Ben Myers
2014-09-11 20:53 ` [PATCH 03/13] libxfs: add xfs_nameops.normhash Ben Myers
2014-09-11 20:55 ` [PATCH 04/13] libxfs: change interface of xfs_nameops.normhash Ben Myers
2014-09-11 20:56 ` [PATCH 05/13] libxfs: add a superblock feature bit to indicate UTF-8 support Ben Myers
2014-09-11 20:57 ` [PATCH 06/13] xfsprogs: add unicode character database files Ben Myers
2014-09-11 20:59 ` [PATCH 07/13] libxfs: add trie generator and supporting code for UTF-8 Ben Myers
2014-09-11 21:00 ` [PATCH 08/13] libxfs: add xfs_nameops for utf8 and utf8+casefold Ben Myers
2014-09-11 21:01 ` [PATCH 09/13] libxfs: apply utf-8 normalization rules to user extended attribute names Ben Myers
2014-09-11 21:02 ` [PATCH 10/13] xfsprogs: add utf8 support to growfs Ben Myers
2014-09-11 21:03 ` [PATCH 11/13] xfsprogs: add utf8 support to mkfs.xfs Ben Myers
2014-09-11 21:04 ` [PATCH 12/13] xfsprogs: add utf8 support to xfs_repair Ben Myers
2014-09-11 21:06 ` [PATCH 13/13] xfsprogs: add a preliminary test for utf8 support Ben Myers
2014-09-12 10:02 ` [RFC] Unicode/UTF-8 support for XFS Dave Chinner
2014-09-12 11:55 ` Olaf Weber
2014-09-12 20:55 ` Christoph Hellwig
2014-09-15 7:16 ` Olaf Weber
2014-09-16 20:54 ` Dave Chinner [this message]
2014-09-16 21:02 ` Christoph Hellwig
2014-09-16 21:42 ` Ben Myers
2014-09-12 17:45 ` Josef 'Jeff' Sipek
2014-09-12 20:53 ` Christoph Hellwig
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=20140916205406.GJ4322@dastard \
--to=david@fromorbit.com \
--cc=bpm@sgi.com \
--cc=hch@infradead.org \
--cc=olaf@sgi.com \
--cc=tinguely@sgi.com \
--cc=xfs@oss.sgi.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