linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: "André Almeida" <andrealmeid@igalia.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Theodore Tso <tytso@mit.edu>,
	linux-unionfs@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	 Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	 kernel-dev@igalia.com,
	Gabriel Krisman Bertazi <krisman@kernel.org>
Subject: Re: [PATCH v5 0/9] ovl: Enable support for casefold layers
Date: Thu, 14 Aug 2025 21:06:21 +0200	[thread overview]
Message-ID: <CAOQ4uxiVFubhiC9Ftwt3kG=RoGSK7rBpPv5Z0GdZfk17dBO6YQ@mail.gmail.com> (raw)
In-Reply-To: <cffb248a-87ce-434e-bd64-2c8112872a18@igalia.com>

On Thu, Aug 14, 2025 at 7:30 PM André Almeida <andrealmeid@igalia.com> wrote:
>
> Em 14/08/2025 14:22, André Almeida escreveu:
> > Hi all,
> >
> > We would like to support the usage of casefold layers with overlayfs to
> > be used with container tools. This use case requires a simple setup,
> > where every layer will have the same encoding setting (i.e. Unicode
> > version and flags), using one upper and one lower layer.
> >
>
> Amir,
>
> I tried to run your xfstest for casefolded ovl[1] but I can see that it
> still requires some work. I tried to fix some of the TODO's but I didn't
> managed to mkfs the base fs with casefold enabled...

When you write mkfs the base fs, I suspect that you are running
check -overlay or something.

This is not how this test should be run.
It should run as a normal test on ext4 or any other fs  that supports casefold.

When you run check -g casefold, the generic test generic/556 will
be run if the test fs supports casefold (e.g. ext4).

The new added test belongs to the same group and should run
if you run check -g casefold if the test fs supports casefold (e.g. ext4).

> but we might as
> well discuss this in a dedicated xfstest email thread if you want to
> send a RFC for the test.
>
> [1]
> https://github.com/amir73il/xfstests/commit/03b3facf60e14cab9fc563ad54893563b4cb18e4
>
>

Can you point me to a branch with your ovl patches, so I can pull it
for testing?

Feel free to fix the 2 minor review comments on v5 in your branch.

Thanks,
Amir.

  reply	other threads:[~2025-08-14 19:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 17:22 [PATCH v5 0/9] ovl: Enable support for casefold layers André Almeida
2025-08-14 17:22 ` [PATCH v5 1/9] fs: Create sb_encoding() helper André Almeida
2025-08-14 17:22 ` [PATCH v5 2/9] fs: Create sb_same_encoding() helper André Almeida
2025-08-14 17:22 ` [PATCH v5 3/9] ovl: Prepare for mounting case-insensitive enabled layers André Almeida
2025-08-14 18:47   ` Amir Goldstein
2025-08-14 17:22 ` [PATCH v5 4/9] ovl: Create ovl_casefold() to support casefolded strncmp() André Almeida
2025-08-14 18:59   ` Amir Goldstein
2025-08-15 16:16   ` Amir Goldstein
2025-08-15 16:53     ` André Almeida
2025-08-17 14:33   ` Amir Goldstein
2025-08-22 14:07     ` André Almeida
2025-08-14 17:22 ` [PATCH v5 5/9] ovl: Ensure that all layers have the same encoding André Almeida
2025-08-14 17:22 ` [PATCH v5 6/9] ovl: Set case-insensitive dentry operations for ovl sb André Almeida
2025-08-15 11:52   ` kernel test robot
2025-08-14 17:22 ` [PATCH v5 7/9] ovl: Add S_CASEFOLD as part of the inode flag to be copied André Almeida
2025-08-14 17:22 ` [PATCH v5 8/9] ovl: Check for casefold consistency when creating new dentries André Almeida
2025-08-14 18:54   ` Amir Goldstein
2025-08-14 17:22 ` [PATCH v5 9/9] ovl: Support mounting case-insensitive enabled layers André Almeida
2025-08-14 18:48   ` Amir Goldstein
2025-08-14 17:30 ` [PATCH v5 0/9] ovl: Enable support for casefold layers André Almeida
2025-08-14 19:06   ` Amir Goldstein [this message]
2025-08-15 13:33     ` André Almeida
2025-08-15 13:50       ` Amir Goldstein
2025-08-17 15:03         ` Amir Goldstein
2025-08-22 14:15           ` André Almeida
2025-08-22 17:21             ` Amir Goldstein
2025-08-22 17:39               ` André Almeida

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='CAOQ4uxiVFubhiC9Ftwt3kG=RoGSK7rBpPv5Z0GdZfk17dBO6YQ@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=andrealmeid@igalia.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=kernel-dev@igalia.com \
    --cc=krisman@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=tytso@mit.edu \
    --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).