From: Eric Biggers <ebiggers@kernel.org>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca, jaegeuk@kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel@collabora.com
Subject: Re: [PATCH v5 4/8] ext4: Reuse generic_ci_match for ci comparisons
Date: Wed, 18 May 2022 12:20:45 -0700 [thread overview]
Message-ID: <YoVHDdMYx5Lbn7aP@sol.localdomain> (raw)
In-Reply-To: <20220518172320.333617-5-krisman@collabora.com>
On Wed, May 18, 2022 at 01:23:16PM -0400, Gabriel Krisman Bertazi wrote:
> Instead of reimplementing ext4_match_ci, use the new libfs helper.
>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
> ---
[...]
> int ext4_fname_setup_ci_filename(struct inode *dir, const struct qstr *iname,
> struct ext4_filename *name)
> {
> @@ -1432,20 +1380,25 @@ static bool ext4_match(struct inode *parent,
> #if IS_ENABLED(CONFIG_UNICODE)
> if (parent->i_sb->s_encoding && IS_CASEFOLDED(parent) &&
> (!IS_ENCRYPTED(parent) || fscrypt_has_encryption_key(parent))) {
> - 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)) {
> + int ret;
>
> - return false;
> - }
> - }
> - return !ext4_ci_compare(parent, &fname->cf_name,
> - de->name, de->name_len, true);
> + if (IS_ENCRYPTED(parent) &&
> + (fname->hinfo.hash != EXT4_DIRENT_HASH(de) ||
> + fname->hinfo.minor_hash != EXT4_DIRENT_MINOR_HASH(de)))
> + return false;
> +
> + ret = generic_ci_match(parent, fname->usr_fname,
> + &fname->cf_name, de->name,
> + de->name_len);
> + if (ret < 0) {
> + /*
> + * Treat comparison errors as not a match. The
> + * only case where it happens is on a disk
> + * corruption or ENOMEM.
> + */
> + return false;
> }
> - return !ext4_ci_compare(parent, fname->usr_fname, de->name,
> - de->name_len, false);
> + return ret;
> }
This needs an explanation for why it's okay to remove
'fname->cf_name.name != NULL' from the condition for doing the hash comparison
for an encrypted+casefolded directory entry.
- Eric
next prev parent reply other threads:[~2022-05-18 19:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 17:23 [PATCH v5 0/8] Clean up the case-insensitive lookup path Gabriel Krisman Bertazi
2022-05-18 17:23 ` [PATCH v5 1/8] ext4: Simplify the handling of cached insensitive names Gabriel Krisman Bertazi
2022-05-18 18:49 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 2/8] f2fs: " Gabriel Krisman Bertazi
2022-05-18 18:54 ` Eric Biggers
2022-05-19 11:27 ` [f2fs-dev] " Chao Yu
2022-05-19 11:32 ` Chao Yu
2022-05-18 17:23 ` [PATCH v5 3/8] libfs: Introduce case-insensitive string comparison helper Gabriel Krisman Bertazi
2022-05-18 19:05 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 4/8] ext4: Reuse generic_ci_match for ci comparisons Gabriel Krisman Bertazi
2022-05-18 19:20 ` Eric Biggers [this message]
2022-05-18 22:44 ` Gabriel Krisman Bertazi
2022-05-18 17:23 ` [PATCH v5 5/8] f2fs: " Gabriel Krisman Bertazi
2022-05-18 19:22 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 6/8] ext4: Log error when lookup of encoded dentry fails Gabriel Krisman Bertazi
2022-05-18 19:23 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 7/8] ext4: Move CONFIG_UNICODE defguards into the code flow Gabriel Krisman Bertazi
2022-05-18 19:25 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 8/8] f2fs: " Gabriel Krisman Bertazi
2022-05-18 19:26 ` Eric Biggers
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=YoVHDdMYx5Lbn7aP@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).