From: "André Almeida" <andrealmeid@igalia.com>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
krisman@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kernel-dev@igalia.com, Daniel Rosenberg <drosen@google.com>,
smcv@collabora.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 6/8] tmpfs: Add flag FS_CASEFOLD_FL support for tmpfs dirs
Date: Wed, 4 Sep 2024 19:28:16 -0300 [thread overview]
Message-ID: <500ff1ba-d8db-4f4d-9084-6d59401992da@igalia.com> (raw)
In-Reply-To: <87jzfshfwn.fsf@mailhost.krisman.be>
Hi Krisman,
Thanks for the feedback!
Em 03/09/2024 13:15, Gabriel Krisman Bertazi escreveu:
> André Almeida <andrealmeid@igalia.com> writes:
>
>> Enable setting flag FS_CASEFOLD_FL for tmpfs directories, when tmpfs is
>> mounted with casefold support. A special check is need for this flag,
>> since it can't be set for non-empty directories.
>>
>> Signed-off-by: André Almeida <andrealmeid@igalia.com>
[...]
>> +
>> + if (fsflags & FS_CASEFOLD_FL) {
>> + if (!sb->s_encoding)
>> + return -EOPNOTSUPP;
>> +
>> + if (!S_ISDIR(inode->i_mode))
>> + return -ENOTDIR;
>> +
>> + if (dentry && !simple_empty(dentry))
>> + return -ENOTEMPTY;
>> +
>> + i_flags |= S_CASEFOLD;
>> + } else if (old & S_CASEFOLD) {
>> + if (dentry && !simple_empty(dentry))
>> + return -ENOTEMPTY;
>
> We don't want to fail if a directory already has the S_CASEFOLD
> flag and we are not flipping it in the current operation. Something like:
>
> if ((fsflags ^ old) & S_CASEFOLD) {
> if (!sb->s_encoding)
> return -EOPNOTSUPP;
>
> if (!S_ISDIR(inode->i_mode))
> return -ENOTDIR;
>
> if (dentry && !simple_empty(dentry))
> return -ENOTEMPTY;
> i_flags |= fsflags & S_CASEFOLD;
> }
>
You are right, it's broken and failing for directories with S_CASEFOLD.
Here's a small test showing that we can't add the +d attribute to a
non-empty CI folder (+d doesn't require the directory to be empty):
folder ) mkdir A
folder ) mkdir A/B
folder ) chattr +d A/B
folder ) chattr +d A
chattr: Directory not empty while setting flags on A
However, FS_CASEFOLD_FL != S_CASEFOLD and the set of values for
inode->i_flags (var old) and fsflags aren't the same, so your proposed
snippet didn't work. I see that ext4 has a very similar code as your
proposal, but I think they do something different with the flag values.
I rewrote my code separating the three possible paths and it worked:
/* inheritance from parent dir/keeping the same flags path */
if ((fsflags & FS_CASEFOLD_FL) && (old & S_CASEFOLD))
i_flags |= S_CASEFOLD;
/* removing flag path */
if (!(fsflags & FS_CASEFOLD_FL) && (old & S_CASEFOLD))
if (dentry && !simple_empty(dentry))
return -ENOTEMPTY;
/* adding flag path */
if ((fsflags & FS_CASEFOLD_FL) && !(old & S_CASEFOLD)) {
if (!sb->s_encoding)
return -EOPNOTSUPP;
if (!S_ISDIR(inode->i_mode))
return -ENOTDIR;
if (dentry && !simple_empty(dentry))
return -ENOTEMPTY;
i_flags |= S_CASEFOLD;
}
In that way, the `chattr +d` call doesn't fall into the simple_empty()
check. I simplified the code like this for the v3:
if (fsflags & FS_CASEFOLD_FL) {
if (!(old & S_CASEFOLD)) {
if (!sb->s_encoding)
return -EOPNOTSUPP;
if (!S_ISDIR(inode->i_mode))
return -ENOTDIR;
if (dentry && !simple_empty(dentry))
return -ENOTEMPTY;
}
i_flags |= S_CASEFOLD;
} else if (old & S_CASEFOLD) {
if (dentry && !simple_empty(dentry))
return -ENOTEMPTY;
}
next prev parent reply other threads:[~2024-09-04 22:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 22:55 [PATCH v2 0/8] tmpfs: Add case-insesitive support for tmpfs André Almeida
2024-09-02 22:55 ` [PATCH v2 1/8] unicode: Fix utf8_load() error path André Almeida
2024-09-03 11:40 ` Theodore Ts'o
2024-09-03 16:48 ` Gabriel Krisman Bertazi
2024-09-02 22:55 ` [PATCH v2 2/8] unicode: Create utf8_check_strict_name André Almeida
2024-09-03 9:04 ` kernel test robot
2024-09-03 11:36 ` Theodore Ts'o
2024-09-03 15:34 ` Gabriel Krisman Bertazi
2024-09-02 22:55 ` [PATCH v2 3/8] ext4: Use utf8_check_strict_name helper André Almeida
2024-09-03 11:37 ` Theodore Ts'o
2024-09-02 22:55 ` [PATCH v2 4/8] unicode: Recreate utf8_parse_version() André Almeida
2024-09-03 11:41 ` Theodore Ts'o
2024-09-02 22:55 ` [PATCH v2 5/8] tmpfs: Add casefold lookup support André Almeida
2024-09-03 16:08 ` Gabriel Krisman Bertazi
2024-09-02 22:55 ` [PATCH v2 6/8] tmpfs: Add flag FS_CASEFOLD_FL support for tmpfs dirs André Almeida
2024-09-03 9:04 ` kernel test robot
2024-09-03 9:04 ` kernel test robot
2024-09-03 16:15 ` Gabriel Krisman Bertazi
2024-09-04 22:28 ` André Almeida [this message]
2024-09-02 22:55 ` [PATCH v2 7/8] tmpfs: Expose filesystem features via sysfs André Almeida
2024-09-02 22:55 ` [PATCH v2 8/8] docs: tmpfs: Add casefold options André Almeida
2024-09-03 16:38 ` Gabriel Krisman Bertazi
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=500ff1ba-d8db-4f4d-9084-6d59401992da@igalia.com \
--to=andrealmeid@igalia.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=drosen@google.com \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kernel-dev@igalia.com \
--cc=krisman@kernel.org \
--cc=krisman@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=smcv@collabora.com \
--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