From: Amir Goldstein <amir73il@gmail.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-fsdevel@vger.kernel.org, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 0/6] overlayfs + casefolding
Date: Fri, 23 May 2025 19:14:26 +0200 [thread overview]
Message-ID: <CAOQ4uxisCFNuHtSJoP19525BDdfeN2ukehj_-7PxepSTDOte9w@mail.gmail.com> (raw)
In-Reply-To: <q6o6jrgwpdt67xsztsqjmewt66kjv6btyayazk7zlk4zjoww4n@2zzowgibx5ka>
On Fri, May 23, 2025 at 4:10 PM Kent Overstreet
<kent.overstreet@linux.dev> wrote:
>
> On Tue, May 20, 2025 at 04:33:14PM +0200, Amir Goldstein wrote:
> > I am saying that IMO a smaller impact (and less user friendly) fix is more
> > appropriate way to deal with this problem.
>
> What do you think about doing your approach as a stopgap?
>
> It seems this is hitting a lot of people, something we can backport to
> 6.15 would be good to have.
Yes, I think I can do that.
Will try to get to it next week.
Thanks,
Amir.
next prev parent reply other threads:[~2025-05-23 17:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 5:15 [PATCH 0/6] overlayfs + casefolding Kent Overstreet
2025-05-20 5:15 ` [PATCH 1/6] bcachefs: BCH_INODE_has_case_insensitive Kent Overstreet
2025-05-20 5:15 ` [PATCH 2/6] darray: lift from bcachefs Kent Overstreet
2025-05-20 5:15 ` [PATCH 3/6] fs: SB_CASEFOLD Kent Overstreet
2025-05-20 5:15 ` [PATCH 4/6] fs: dcache locking for exlusion between overlayfs, casefolding Kent Overstreet
2025-05-20 15:25 ` Al Viro
2025-05-20 15:27 ` Kent Overstreet
2025-05-23 11:54 ` [PATCH v2] fs: dcache " Kent Overstreet
2025-05-20 5:15 ` [PATCH 5/6] bcachefs: Hook up d_casefold_enable() Kent Overstreet
2025-05-20 5:15 ` [PATCH 6/6] overlayfs: Support casefolded filesystems Kent Overstreet
2025-05-20 8:05 ` [PATCH 0/6] overlayfs + casefolding Amir Goldstein
2025-05-20 12:25 ` Kent Overstreet
2025-05-20 12:40 ` Amir Goldstein
2025-05-20 12:43 ` Kent Overstreet
2025-05-20 14:03 ` Amir Goldstein
2025-05-20 14:12 ` Kent Overstreet
2025-05-20 14:33 ` Amir Goldstein
2025-05-20 14:44 ` Kent Overstreet
2025-05-20 15:13 ` Amir Goldstein
2025-05-20 15:21 ` Kent Overstreet
2025-05-20 16:40 ` Miklos Szeredi
2025-05-20 16:49 ` Kent Overstreet
2025-05-23 14:10 ` Kent Overstreet
2025-05-23 17:14 ` Amir Goldstein [this message]
2025-05-23 20:30 ` Amir Goldstein
2025-05-23 21:09 ` Kent Overstreet
2025-05-24 13:01 ` Amir Goldstein
2025-05-25 18:27 ` Kent Overstreet
2025-05-27 8:57 ` Amir Goldstein
2025-05-27 18:07 ` Kent Overstreet
2025-05-20 18:49 ` John Stoffel
2025-05-21 1:49 ` Kent Overstreet
2025-05-22 21:44 ` John Stoffel
2025-05-21 11:26 ` Malte Schröder
2025-05-22 7:53 ` Christopher Snowhill
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=CAOQ4uxisCFNuHtSJoP19525BDdfeN2ukehj_-7PxepSTDOte9w@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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).