From: Eric Biggers <ebiggers@kernel.org>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: tytso@mit.edu, jaegeuk@kernel.org, linux-ext4@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH 2/5] ext4: Simplify the handling of chached insensitive names
Date: Mon, 28 Mar 2022 20:01:52 -0700 [thread overview]
Message-ID: <YkJ2oFqrYf80PHcm@sol.localdomain> (raw)
In-Reply-To: <20220322030004.148560-3-krisman@collabora.com>
On Mon, Mar 21, 2022 at 11:00:01PM -0400, Gabriel Krisman Bertazi wrote:
> Keeping it as qstr avoids the unnecessary conversion in ext4_match
>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
> ---
> fs/ext4/ext4.h | 2 +-
> fs/ext4/namei.c | 23 +++++++++++------------
> 2 files changed, 12 insertions(+), 13 deletions(-)
>
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index bcd3b9bf8069..46e729ce7b35 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -2484,7 +2484,7 @@ struct ext4_filename {
> struct fscrypt_str crypto_buf;
> #endif
> #if IS_ENABLED(CONFIG_UNICODE)
> - struct fscrypt_str cf_name;
> + struct qstr cf_name;
> #endif
> };
>
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
> index 24ea3bb446d0..8976e5a28c73 100644
> --- a/fs/ext4/namei.c
> +++ b/fs/ext4/namei.c
> @@ -1382,28 +1382,29 @@ static int ext4_ci_compare(const struct inode *parent, const struct qstr *name,
> int ext4_fname_setup_ci_filename(struct inode *dir, const struct qstr *iname,
> struct ext4_filename *name)
> {
> - struct fscrypt_str *cf_name = &name->cf_name;
> + struct qstr *cf_name = &name->cf_name;
> + unsigned char *buf;
> struct dx_hash_info *hinfo = &name->hinfo;
> int len;
>
> if (!IS_CASEFOLDED(dir) || !dir->i_sb->s_encoding ||
> (IS_ENCRYPTED(dir) && !fscrypt_has_encryption_key(dir))) {
> - cf_name->name = NULL;
> + name->cf_name.name = NULL;
> return 0;
> }
Why not keep "cf_name->name = NULL;" above?
- Eric
next prev parent reply other threads:[~2022-03-29 3:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 2:59 [PATCH 0/5] Clean up the case-insenstive lookup path Gabriel Krisman Bertazi
2022-03-22 3:00 ` [PATCH 1/5] ext4: Match the f2fs ci_compare implementation Gabriel Krisman Bertazi
2022-03-29 2:58 ` Eric Biggers
2022-03-22 3:00 ` [PATCH 2/5] ext4: Simplify the handling of chached insensitive names Gabriel Krisman Bertazi
2022-03-29 3:01 ` Eric Biggers [this message]
2022-03-22 3:00 ` [PATCH 3/5] ext4: Implement ci comparison using fscrypt_name Gabriel Krisman Bertazi
2022-03-29 3:08 ` Eric Biggers
2022-03-29 16:11 ` Gabriel Krisman Bertazi
2022-03-31 21:43 ` Eric Biggers
2022-04-04 19:59 ` Gabriel Krisman Bertazi
2022-03-22 3:00 ` [PATCH 4/5] ext4: Simplify hash check on ext4_match Gabriel Krisman Bertazi
2022-03-22 3:00 ` [PATCH 5/5] ext4: Log error when lookup of encoded dentry fails Gabriel Krisman Bertazi
2022-03-29 3:21 ` 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=YkJ2oFqrYf80PHcm@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--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