From: Christian Brauner <brauner@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org,
Kent Overstreet <kent.overstreet@linux.dev>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH v3] ovl: support layers on case-folding capable filesystems
Date: Mon, 23 Jun 2025 12:27:25 +0200 [thread overview]
Message-ID: <20250623-zuversicht-rasten-22993cf67abd@brauner> (raw)
In-Reply-To: <20250602171702.1941891-1-amir73il@gmail.com>
On Mon, 02 Jun 2025 19:17:02 +0200, Amir Goldstein wrote:
> Case folding is often applied to subtrees and not on an entire
> filesystem.
>
> Disallowing layers from filesystems that support case folding is over
> limiting.
>
> Replace the rule that case-folding capable are not allowed as layers
> with a rule that case folded directories are not allowed in a merged
> directory stack.
>
> [...]
Applied to the vfs-6.17.file branch of the vfs/vfs.git tree.
Patches in the vfs-6.17.file branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.17.file
[1/1] ovl: support layers on case-folding capable filesystems
https://git.kernel.org/vfs/vfs/c/5810e7558fda
next prev parent reply other threads:[~2025-06-23 10:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 17:17 [PATCH v3] ovl: support layers on case-folding capable filesystems Amir Goldstein
2025-06-04 4:43 ` Kent Overstreet
2025-06-15 19:20 ` Kent Overstreet
2025-06-16 8:06 ` Amir Goldstein
2025-06-16 12:28 ` Kent Overstreet
2025-06-16 12:36 ` Amir Goldstein
2025-06-16 12:54 ` Kent Overstreet
2025-06-16 15:01 ` Amir Goldstein
2025-06-22 7:20 ` Amir Goldstein
2025-06-22 7:36 ` Amir Goldstein
2025-06-23 10:26 ` Christian Brauner
2025-06-23 10:31 ` Amir Goldstein
2025-06-26 13:37 ` Kent Overstreet
2025-06-26 13:44 ` Amir Goldstein
2025-06-23 10:27 ` Christian Brauner [this message]
2025-06-30 11:33 ` Miklos Szeredi
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=20250623-zuversicht-rasten-22993cf67abd@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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