From: Eric Biggers <ebiggers@kernel.org>
To: Eugen Hristev <eugen.hristev@collabora.com>
Cc: krisman@suse.de, brauner@kernel.org, kernel@collabora.com,
tytso@mit.edu, jack@suse.cz, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, adilger.kernel@dilger.ca,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
jaegeuk@kernel.org, linux-ext4@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [f2fs-dev] [PATCH v17 3/7] libfs: Introduce case-insensitive string comparison helper
Date: Thu, 30 May 2024 21:48:51 -0700 [thread overview]
Message-ID: <20240531044851.GE6505@sol.localdomain> (raw)
In-Reply-To: <20240529082634.141286-4-eugen.hristev@collabora.com>
On Wed, May 29, 2024 at 11:26:30AM +0300, Eugen Hristev via Linux-f2fs-devel wrote:
> + /*
> + * Attempt a case-sensitive match first. It is cheaper and
> + * should cover most lookups, including all the sane
> + * applications that expect a case-sensitive filesystem.
> + */
> +
> + if (dirent.len == (folded_name->name ? folded_name->len : name->len) &&
> + !memcmp(name->name, dirent.name, dirent.len))
> + goto out;
Shouldn't it be just 'name->len' instead of
'(folded_name->name ? folded_name->len : name->len)'?
- 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:[~2024-05-31 4:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 8:26 [f2fs-dev] [PATCH v17 0/7] Case insensitive cleanup for ext4/f2fs Eugen Hristev via Linux-f2fs-devel
2024-05-29 8:26 ` [f2fs-dev] [PATCH v17 1/7] ext4: Simplify the handling of cached casefolded names Eugen Hristev via Linux-f2fs-devel
2024-05-29 8:26 ` [f2fs-dev] [PATCH v17 2/7] f2fs: " Eugen Hristev via Linux-f2fs-devel
2024-05-29 8:26 ` [f2fs-dev] [PATCH v17 3/7] libfs: Introduce case-insensitive string comparison helper Eugen Hristev via Linux-f2fs-devel
2024-05-31 4:48 ` Eric Biggers [this message]
2024-05-31 10:12 ` Eugen Hristev via Linux-f2fs-devel
2024-06-04 19:18 ` Gabriel Krisman Bertazi
2024-05-29 8:26 ` [f2fs-dev] [PATCH v17 4/7] ext4: Reuse generic_ci_match for ci comparisons Eugen Hristev via Linux-f2fs-devel
2024-06-04 19:17 ` Gabriel Krisman Bertazi
2024-06-05 10:48 ` Eugen Hristev via Linux-f2fs-devel
2024-05-29 8:26 ` [f2fs-dev] [PATCH v17 5/7] f2fs: " Eugen Hristev via Linux-f2fs-devel
2024-05-29 8:26 ` [f2fs-dev] [PATCH v17 6/7] ext4: Move CONFIG_UNICODE defguards into the code flow Eugen Hristev via Linux-f2fs-devel
2024-05-29 8:26 ` [f2fs-dev] [PATCH v17 7/7] f2fs: " Eugen Hristev via Linux-f2fs-devel
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=20240531044851.GE6505@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=eugen.hristev@collabora.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=krisman@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).