From: Eric Biggers <ebiggers@kernel.org>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
linux-f2fs-devel@lists.sourceforge.net, adilger.kernel@dilger.ca,
jaegeuk@kernel.org, kernel@collabora.com
Subject: Re: [f2fs-dev] [PATCH v4 05/10] ext4: Simplify hash check on ext4_match
Date: Wed, 11 May 2022 22:46:10 -0700 [thread overview]
Message-ID: <YnyfIn6AuDw/ImUi@sol.localdomain> (raw)
In-Reply-To: <20220511193146.27526-6-krisman@collabora.com>
On Wed, May 11, 2022 at 03:31:41PM -0400, Gabriel Krisman Bertazi wrote:
> The existence of fname->cf_name.name requires s_encoding & IS_CASEFOLDED,
> therefore this can be simplified.
>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
> ---
> fs/ext4/namei.c | 20 +++++++-------------
> 1 file changed, 7 insertions(+), 13 deletions(-)
>
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
> index 5296ced2e43e..cebbcabf0ff0 100644
> --- a/fs/ext4/namei.c
> +++ b/fs/ext4/namei.c
> @@ -1438,25 +1438,19 @@ static bool ext4_match(struct inode *parent,
> #endif
>
> #if IS_ENABLED(CONFIG_UNICODE)
> - if (parent->i_sb->s_encoding && IS_CASEFOLDED(parent) &&
> - (!IS_ENCRYPTED(parent) || fscrypt_has_encryption_key(parent))) {
> + if (IS_ENCRYPTED(parent) && fname->cf_name.name) {
> + if (fname->hinfo.hash != EXT4_DIRENT_HASH(de) ||
> + fname->hinfo.minor_hash != EXT4_DIRENT_MINOR_HASH(de))
> + return false;
> + }
> +
> + if (parent->i_sb->s_encoding && IS_CASEFOLDED(parent)) {
> struct unicode_name u = {
> .folded_name = &fname->cf_name,
> .usr_name = fname->usr_fname
> };
> int ret;
>
> - if (fname->cf_name.name) {
> - if (IS_ENCRYPTED(parent)) {
> - if (fname->hinfo.hash != EXT4_DIRENT_HASH(de) ||
> - fname->hinfo.minor_hash !=
> - EXT4_DIRENT_MINOR_HASH(de)) {
> -
> - return false;
> - }
> - }
> - }
> -
I don't think it's correct to delete the check for the encryption key here. If
lookup is by no-key name, then fscrypt_match_name() must be used, not
generic_ci_match(). And unlike f2fs, ext4 doesn't keep track of whether the
whole lookup is by no-key name; ext4 relies on this fscrypt_has_encryption_key()
check at the last minute when doing each individual comparison. (Which is not
great, but that's how it works now.)
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-05-12 5:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 19:31 [f2fs-dev] [PATCH v4 00/10] Clean up the case-insensitive lookup path Gabriel Krisman Bertazi
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 01/10] ext4: Match the f2fs ci_compare implementation Gabriel Krisman Bertazi
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 02/10] ext4: Simplify the handling of cached insensitive names Gabriel Krisman Bertazi
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 03/10] f2fs: " Gabriel Krisman Bertazi
2022-05-12 4:49 ` Eric Biggers
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 04/10] ext4: Implement ci comparison using unicode_name Gabriel Krisman Bertazi
2022-05-12 5:35 ` Eric Biggers
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 05/10] ext4: Simplify hash check on ext4_match Gabriel Krisman Bertazi
2022-05-12 5:46 ` Eric Biggers [this message]
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 06/10] ext4: Log error when lookup of encoded dentry fails Gabriel Krisman Bertazi
2022-05-12 5:48 ` Eric Biggers
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 07/10] ext4: Move ext4_match_ci into libfs Gabriel Krisman Bertazi
2022-05-12 5:24 ` Eric Biggers
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 08/10] f2fs: Reuse generic_ci_match for ci comparisons Gabriel Krisman Bertazi
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 09/10] ext4: Move CONFIG_UNICODE defguards into the code flow Gabriel Krisman Bertazi
2022-05-12 4:59 ` Eric Biggers
2022-05-11 19:31 ` [f2fs-dev] [PATCH v4 10/10] f2fs: " Gabriel Krisman Bertazi
2022-05-12 4:55 ` Eric Biggers
2022-05-17 19:37 ` [f2fs-dev] [PATCH v4 00/10] Clean up the case-insensitive lookup path Theodore Ts'o
2022-05-17 19:57 ` Gabriel Krisman Bertazi
2022-05-18 0:15 ` Theodore Ts'o
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=YnyfIn6AuDw/ImUi@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=jaegeuk@kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=tytso@mit.edu \
/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).