From: Eric Biggers <ebiggers@kernel.org> To: linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu> Cc: linux-fsdevel@vger.kernel.org, Gabriel Krisman Bertazi <krisman@suse.de>, linux-f2fs-devel@lists.sourceforge.net Subject: [f2fs-dev] [PATCH 3/3] libfs: remove redundant checks of s_encoding Date: Mon, 14 Aug 2023 11:29:03 -0700 [thread overview] Message-ID: <20230814182903.37267-4-ebiggers@kernel.org> (raw) In-Reply-To: <20230814182903.37267-1-ebiggers@kernel.org> From: Eric Biggers <ebiggers@google.com> Now that neither ext4 nor f2fs allows inodes with the casefold flag to be instantiated when unsupported, it's unnecessary to repeatedly check for support later on during random filesystem operations. Signed-off-by: Eric Biggers <ebiggers@google.com> --- fs/libfs.c | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/fs/libfs.c b/fs/libfs.c index 5b851315eeed..5197ea8c66d3 100644 --- a/fs/libfs.c +++ b/fs/libfs.c @@ -1381,16 +1381,6 @@ bool is_empty_dir_inode(struct inode *inode) } #if IS_ENABLED(CONFIG_UNICODE) -/* - * Determine if the name of a dentry should be casefolded. - * - * Return: if names will need casefolding - */ -static bool needs_casefold(const struct inode *dir) -{ - return IS_CASEFOLDED(dir) && dir->i_sb->s_encoding; -} - /** * generic_ci_d_compare - generic d_compare implementation for casefolding filesystems * @dentry: dentry whose name we are checking against @@ -1411,7 +1401,7 @@ static int generic_ci_d_compare(const struct dentry *dentry, unsigned int len, char strbuf[DNAME_INLINE_LEN]; int ret; - if (!dir || !needs_casefold(dir)) + if (!dir || !IS_CASEFOLDED(dir)) goto fallback; /* * If the dentry name is stored in-line, then it may be concurrently @@ -1453,7 +1443,7 @@ static int generic_ci_d_hash(const struct dentry *dentry, struct qstr *str) const struct unicode_map *um = sb->s_encoding; int ret = 0; - if (!dir || !needs_casefold(dir)) + if (!dir || !IS_CASEFOLDED(dir)) return 0; ret = utf8_casefold_hash(um, dentry, str); -- 2.41.0 _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org> To: linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu> Cc: linux-fsdevel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Gabriel Krisman Bertazi <krisman@suse.de> Subject: [PATCH 3/3] libfs: remove redundant checks of s_encoding Date: Mon, 14 Aug 2023 11:29:03 -0700 [thread overview] Message-ID: <20230814182903.37267-4-ebiggers@kernel.org> (raw) In-Reply-To: <20230814182903.37267-1-ebiggers@kernel.org> From: Eric Biggers <ebiggers@google.com> Now that neither ext4 nor f2fs allows inodes with the casefold flag to be instantiated when unsupported, it's unnecessary to repeatedly check for support later on during random filesystem operations. Signed-off-by: Eric Biggers <ebiggers@google.com> --- fs/libfs.c | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/fs/libfs.c b/fs/libfs.c index 5b851315eeed..5197ea8c66d3 100644 --- a/fs/libfs.c +++ b/fs/libfs.c @@ -1381,16 +1381,6 @@ bool is_empty_dir_inode(struct inode *inode) } #if IS_ENABLED(CONFIG_UNICODE) -/* - * Determine if the name of a dentry should be casefolded. - * - * Return: if names will need casefolding - */ -static bool needs_casefold(const struct inode *dir) -{ - return IS_CASEFOLDED(dir) && dir->i_sb->s_encoding; -} - /** * generic_ci_d_compare - generic d_compare implementation for casefolding filesystems * @dentry: dentry whose name we are checking against @@ -1411,7 +1401,7 @@ static int generic_ci_d_compare(const struct dentry *dentry, unsigned int len, char strbuf[DNAME_INLINE_LEN]; int ret; - if (!dir || !needs_casefold(dir)) + if (!dir || !IS_CASEFOLDED(dir)) goto fallback; /* * If the dentry name is stored in-line, then it may be concurrently @@ -1453,7 +1443,7 @@ static int generic_ci_d_hash(const struct dentry *dentry, struct qstr *str) const struct unicode_map *um = sb->s_encoding; int ret = 0; - if (!dir || !needs_casefold(dir)) + if (!dir || !IS_CASEFOLDED(dir)) return 0; ret = utf8_casefold_hash(um, dentry, str); -- 2.41.0
next prev parent reply other threads:[~2023-08-14 18:29 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-14 18:29 [f2fs-dev] [PATCH 0/3] Simplify rejection of unexpected casefold inode flag Eric Biggers 2023-08-14 18:29 ` Eric Biggers 2023-08-14 18:29 ` [f2fs-dev] [PATCH 1/3] ext4: reject casefold inode flag without casefold feature Eric Biggers 2023-08-14 18:29 ` Eric Biggers 2023-08-14 19:09 ` [f2fs-dev] " Gabriel Krisman Bertazi 2023-08-14 19:09 ` Gabriel Krisman Bertazi 2023-08-14 19:24 ` Eric Biggers 2023-08-14 19:24 ` [f2fs-dev] " Eric Biggers 2023-08-14 19:52 ` Gabriel Krisman Bertazi 2023-08-14 19:52 ` Gabriel Krisman Bertazi 2023-08-14 18:29 ` [f2fs-dev] [PATCH 2/3] ext4: remove redundant checks of s_encoding Eric Biggers 2023-08-14 18:29 ` Eric Biggers 2023-08-14 18:29 ` Eric Biggers [this message] 2023-08-14 18:29 ` [PATCH 3/3] libfs: " Eric Biggers 2023-08-24 4:53 ` [f2fs-dev] [PATCH 0/3] Simplify rejection of unexpected casefold inode flag Theodore Ts'o 2023-08-24 4:53 ` Theodore Ts'o 2023-09-04 18:11 ` [f2fs-dev] " patchwork-bot+f2fs 2023-09-04 18:11 ` patchwork-bot+f2fs
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=20230814182903.37267-4-ebiggers@kernel.org \ --to=ebiggers@kernel.org \ --cc=krisman@suse.de \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-fsdevel@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.