From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: "André Almeida" <andrealmeid@igalia.com>
Cc: Gabriel Krisman Bertazi <gabriel@krisman.be>,
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>,
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>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH v4 07/10] tmpfs: Add casefold lookup support
Date: Wed, 02 Oct 2024 17:29:29 -0400 [thread overview]
Message-ID: <877caqw5vq.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <c547e1aa-f894-409e-9033-f370c5c16171@igalia.com> (=?utf-8?Q?=22Andr=C3=A9?= Almeida"'s message of "Tue, 1 Oct 2024 22:40:17 -0300")
André Almeida <andrealmeid@igalia.com> writes:
> Hey Krisman,
>
> Em 12/09/2024 16:04, Gabriel Krisman Bertazi escreveu:
>> André Almeida <andrealmeid@igalia.com> writes:
>>
>
> [...]
>
>>> +#if IS_ENABLED(CONFIG_UNICODE)
>>> + if (ctx->encoding) {
>>> + sb->s_encoding = ctx->encoding;
>>> + sb->s_d_op = &shmem_ci_dentry_ops;
>>> + if (ctx->strict_encoding)
>>> + sb->s_encoding_flags = SB_ENC_STRICT_MODE_FL;
>>> + }
>>> #else
>>> - sb->s_flags |= SB_NOUSER;
>>> + sb->s_d_op = &simple_dentry_operations;
>> Moving simple_dentry_operations to be set at s_d_op should be a
>> separate
>> patch.
>> It is a change that has non-obvious side effects (i.e. the way we
>> treat the root dentry) so it needs proper review by itself. It is
>> also not related to the rest of the case-insensitive patch.
>>
>
> The idea of setting simple_dentry_operations come from my previous
> approach of having our own shmem_lookup(), replacing
> simple_lookup(). Now that we are settled to keep with simple_lookup()
> anyway (that already sets simple_dentry_operations), I think we don't
> need this change anymore, right?
Up to you, really. If you don't need it to support casefold lookup in
tmpfs, it doesn't need to be part of the same patchset.
> This will be set for every dentry that doesn't have a
> dentry->d_sb->s_d_op. Case-insensitive mount points will have this set,
> so we don't risk overwriting it.
I encourage you to send a new version with this. makes sense to me.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2024-10-02 21:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 14:44 [PATCH v4 00/10] tmpfs: Add case-insensitive support for tmpfs André Almeida
2024-09-11 14:44 ` [PATCH v4 01/10] libfs: Create the helper function generic_ci_validate_strict_name() André Almeida
2024-09-12 19:16 ` Gabriel Krisman Bertazi
2024-09-11 14:44 ` [PATCH v4 02/10] ext4: Use generic_ci_validate_strict_name helper André Almeida
2024-09-12 19:14 ` Gabriel Krisman Bertazi
2024-09-11 14:44 ` [PATCH v4 03/10] unicode: Recreate utf8_parse_version() André Almeida
2024-09-12 19:14 ` Gabriel Krisman Bertazi
2024-09-11 14:44 ` [PATCH v4 04/10] unicode: Export latest available UTF-8 version number André Almeida
2024-09-11 14:44 ` [PATCH v4 05/10] libfs: Check for casefold dirs on simple_lookup() André Almeida
2024-09-11 14:44 ` [PATCH v4 06/10] libfs: Export generic_ci_ dentry functions André Almeida
2024-09-12 19:13 ` Gabriel Krisman Bertazi
2024-09-11 14:44 ` [PATCH v4 07/10] tmpfs: Add casefold lookup support André Almeida
2024-09-12 19:04 ` Gabriel Krisman Bertazi
2024-10-02 1:40 ` André Almeida
2024-10-02 21:29 ` Gabriel Krisman Bertazi [this message]
2024-09-13 16:28 ` kernel test robot
2024-09-13 18:25 ` kernel test robot
2024-09-11 14:45 ` [PATCH v4 08/10] tmpfs: Add flag FS_CASEFOLD_FL support for tmpfs dirs André Almeida
2024-09-12 19:10 ` Gabriel Krisman Bertazi
2024-09-11 14:45 ` [PATCH v4 09/10] tmpfs: Expose filesystem features via sysfs André Almeida
2024-09-12 19:07 ` Gabriel Krisman Bertazi
2024-09-11 14:45 ` [PATCH v4 10/10] docs: tmpfs: Add casefold options André Almeida
2024-09-12 19:07 ` 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=877caqw5vq.fsf@mailhost.krisman.be \
--to=gabriel@krisman.be \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--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=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=smcv@collabora.com \
--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