From: "André Almeida" <andrealmeid@igalia.com>
To: Gabriel Krisman Bertazi <gabriel@krisman.be>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
smcv@collabora.com, kernel-dev@igalia.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v6 01/10] libfs: Create the helper function generic_ci_validate_strict_name()
Date: Wed, 16 Oct 2024 18:59:58 -0300 [thread overview]
Message-ID: <a26db27a-85ca-46e4-9669-d885db2dd4ae@igalia.com> (raw)
In-Reply-To: <87bjzls6ff.fsf@mailhost.krisman.be>
Em 15/10/2024 12:59, Gabriel Krisman Bertazi escreveu:
> André Almeida <andrealmeid@igalia.com> writes:
>
>> +static inline bool generic_ci_validate_strict_name(struct inode *dir, struct qstr *name)
>> +{
>> + if (!IS_CASEFOLDED(dir) || !sb_has_strict_encoding(dir->i_sb))
>> + return true;
>> +
>> + /*
>> + * A casefold dir must have a encoding set, unless the filesystem
>> + * is corrupted
>> + */
>> + if (WARN_ON_ONCE(!dir->i_sb->s_encoding))
>> + return true;
>> +
>> + return utf8_validate(dir->i_sb->s_encoding, name);
>
> There is something fishy here. Concerningly, the fstests test doesn't
> catch it.
>
> utf8_validate is defined as:
>
> int utf8_validate(const struct unicode_map *um, const struct qstr *str)
>
> Which returns 0 on success and !0 on error. Thus, when casting to bool,
> the return code should be negated.
>
> But generic/556 doesn't fail. That's because we are over cautious, and
> also check the string at the end of generic_ci_d_hash. So we never
> really reach utf8_validate in the tested case.
>
> But if you comment the final if in generic_ci_d_hash, you'll see this
> patchset regresses the fstests case generic/556 over ext4.
>
> We really need the check in both places, though. We don't want to rely
> on the behavior of generic_ci_d_hash to block invalid filenames, as that
> might change.
>
Thanks Krisman! Nice catch. I fixed this for the next version. Testing
with the modified generic_ci_d_hash(), I also realized that the
validation was in the wrong place and leaving an inode behind, this fixed:
diff --git a/mm/shmem.c b/mm/shmem.c
index eb1ea1f3b37c..7bd7ca5777af 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -3624,13 +3624,13 @@ shmem_mknod(struct mnt_idmap *idmap, struct
inode *dir,
struct inode *inode;
int error;
+ if (!generic_ci_validate_strict_name(dir, &dentry->d_name))
+ return -EINVAL;
+
inode = shmem_get_inode(idmap, dir->i_sb, dir, mode, dev,
VM_NORESERVE);
if (IS_ERR(inode))
return PTR_ERR(inode);
- if (!generic_ci_validate_strict_name(dir, &dentry->d_name))
- return -EINVAL;
-
next prev parent reply other threads:[~2024-10-16 22:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 19:39 [PATCH v6 00/10] tmpfs: Add case-insensitive support for tmpfs André Almeida
2024-10-10 19:39 ` [PATCH v6 01/10] libfs: Create the helper function generic_ci_validate_strict_name() André Almeida
2024-10-15 15:59 ` Gabriel Krisman Bertazi
2024-10-16 21:59 ` André Almeida [this message]
2024-10-10 19:39 ` [PATCH v6 02/10] ext4: Use generic_ci_validate_strict_name helper André Almeida
2024-10-10 19:39 ` [PATCH v6 03/10] unicode: Export latest available UTF-8 version number André Almeida
2024-10-15 13:40 ` Gabriel Krisman Bertazi
2024-10-10 19:39 ` [PATCH v6 04/10] unicode: Recreate utf8_parse_version() André Almeida
2024-10-10 19:39 ` [PATCH v6 05/10] libfs: Export generic_ci_ dentry functions André Almeida
2024-10-10 19:39 ` [PATCH v6 06/10] tmpfs: Always set simple_dentry_operations as dentry ops André Almeida
2024-10-10 19:39 ` [PATCH v6 07/10] tmpfs: Add casefold lookup support André Almeida
2024-10-15 18:30 ` Gabriel Krisman Bertazi
2024-10-15 18:35 ` Gabriel Krisman Bertazi
2024-10-10 19:39 ` [PATCH v6 08/10] tmpfs: Add flag FS_CASEFOLD_FL support for tmpfs dirs André Almeida
2024-10-10 19:39 ` [PATCH v6 09/10] tmpfs: Expose filesystem features via sysfs André Almeida
2024-10-10 19:39 ` [PATCH v6 10/10] docs: tmpfs: Add casefold options André Almeida
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=a26db27a-85ca-46e4-9669-d885db2dd4ae@igalia.com \
--to=andrealmeid@igalia.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=gabriel@krisman.be \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kernel-dev@igalia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=smcv@collabora.com \
--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
all inboxes | Powered by JetHome®