[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOQ4uxjHb4B1YL2hSMHxd2Y0mMmfpHMzgbHO5wLF3=rMVxsHyQ@mail.gmail.com>
Date: Sat, 24 May 2025 15:01:44 +0200
From: Amir Goldstein <amir73il@...il.com>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: linux-fsdevel@...r.kernel.org, linux-bcachefs@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-unionfs@...r.kernel.org,
Miklos Szeredi <miklos@...redi.hu>, Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH 0/6] overlayfs + casefolding
On Fri, May 23, 2025 at 11:10 PM Kent Overstreet
<kent.overstreet@...ux.dev> wrote:
>
> On Fri, May 23, 2025 at 10:30:16PM +0200, Amir Goldstein wrote:
>
> That makes fstests generic/631 pass.
Yes, that is not very surprising.
I meant if you could help test that:
1. mounting case folder upperdir/lowerdir fails
2. lookup a case folder subdir fails
3. lookup in a dir that was empty and became case folder while ovl was
mounted fails
For me, I do not have any setup with case folding subtrees
so testing those use cases would take me time and
I think that you must have tested all those scenarios with your patch set?
and maybe already have some fstests for them?
>
> We really should be logging something in dmesg on error due to
> casefolded directory, though.
No problem.
Attached v2 with warnings.
For example, here is the new warning in test overlay/065:
[ 131.815110] overlayfs: failed lookup in lower (/lower,
name='upper', err=-40): overlapping layers
Thanks,
Amir.
View attachment "v2-0001-ovl-support-layers-on-case-folding-capable-filesy.patch" of type "text/x-patch" (5181 bytes)
Powered by blists - more mailing lists