From: Mark Harmstone <mark@harmstone.com>
To: Neal Gompa <ngompa13@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Chris Murphy <lists@colorremedies.com>
Subject: Re: Optional case-insensitivity
Date: Sat, 29 Aug 2020 01:16:40 +0100 [thread overview]
Message-ID: <e5bce3b8-35f5-9c56-3abc-be4be33e875d@harmstone.com> (raw)
In-Reply-To: <CAEg-Je_Mhx2QewCvFbwcV5oVHHa9jkdPcpkFZN8YR_fktCHSCQ@mail.gmail.com>
On 28/8/20 8:43 pm, Neal Gompa wrote:
> Hey,
>
> So I saw today on LWN an article about ext4 gaining the ability to do
> per file/folder case-insensitivity[1]. I can see some value in this
> property existing for subvolume/folder/file level for Btrfs for things
> like Wine and Darling, which could take advantage of this to help
> support Windows and macOS applications that expect insensitivity to
> work properly. In particular, I'm looking at how games are glitchy
> with case sensitivity because it's rarely tested (both Windows and
> macOS are case-insensitive by default).
>
> Has anyone looked at what it would take to do this in Btrfs too?
>
> [1]: https://lwn.net/Articles/829737/
Hi Neal,
FWIW, I emulate the reverse of this, optional case-insensitity, in my Windows
Btrfs driver, by using the xattr user.case_sensitive.
To do it properly, presumably all you'd need to do is add another DIR_INDEX/
DIR_ITEM pair to the inodes in question, though it'd imply another compat_ro
flag. I think it's something I've mentioned to Chris Mason before now.
Mark
prev parent reply other threads:[~2020-08-29 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 19:43 Optional case-insensitivity Neal Gompa
2020-08-28 23:26 ` Chris Murphy
2020-08-28 23:28 ` Chris Murphy
2020-08-29 0:16 ` Mark Harmstone [this message]
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=e5bce3b8-35f5-9c56-3abc-be4be33e875d@harmstone.com \
--to=mark@harmstone.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=ngompa13@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