From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Andreas Dilger <adilger@dilger.ca>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
guy@linux.com, jra@google.com, drosen@google.com,
hch@infradead.org
Subject: Re: [RFC] A proposal for adding case insensitive lookups to ext4
Date: Mon, 7 Nov 2016 15:30:35 +1100 [thread overview]
Message-ID: <20161107043035.GH28177@dastard> (raw)
In-Reply-To: <20161107001456.muvwkwlqxucrzpzi@thunk.org>
On Sun, Nov 06, 2016 at 07:14:56PM -0500, Theodore Ts'o wrote:
> I talked to Christoph at the Plumbers Closing party, and he suggested
> that we get something simple in first which (a) assumes no on-disk
> format changes, (b) does everything in the VFS layer, by using a
> MS_CASE_FOLD, uses a case-insensitive dentry hash, and which degrades
> to a brute force search in the VFS by using readdir interfaces if the
> direct lookup does not succeed, and (c) at least initially assumes
> only ASCII.
>
> This could be extended by individual file systems who are willing to
> make on-disk format changes.
OK, as long people are ok with things going wonky when the
filesystem is mounted without those mount options, I'm not really
fussed...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-11-07 4:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 17:28 [RFC] A proposal for adding case insensitive lookups to ext4 Theodore Ts'o
2016-11-04 16:14 ` Andreas Dilger
2016-11-04 21:51 ` Theodore Ts'o
2016-11-04 23:12 ` Andreas Dilger
2016-11-06 23:57 ` Dave Chinner
2016-11-07 0:14 ` Theodore Ts'o
2016-11-07 4:30 ` Dave Chinner [this message]
2016-11-07 5:42 ` Theodore Ts'o
[not found] ` <CAEuANoLdZ0STmhp+1voS9K6+Ndkb6zfSWEcc0_thUtDjS8NPwg@mail.gmail.com>
2016-11-05 0:00 ` Theodore Ts'o
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=20161107043035.GH28177@dastard \
--to=david@fromorbit.com \
--cc=adilger@dilger.ca \
--cc=drosen@google.com \
--cc=guy@linux.com \
--cc=hch@infradead.org \
--cc=jra@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.