From: Viacheslav Dubeyko <vdubeyko@redhat.com>
To: Thorsten Blum <thorsten.blum@linux.dev>,
Viacheslav Dubeyko <slava@dubeyko.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Yangtao Li <frank.li@vivo.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hfsplus: replace unbounded sprintf() in hfsplus_{lookup,link,unlink}
Date: Fri, 24 Apr 2026 12:38:54 -0700 [thread overview]
Message-ID: <a4d47cc47de0b887202fd73cb93bc02bff4095c8.camel@redhat.com> (raw)
In-Reply-To: <20260424090633.307300-3-thorsten.blum@linux.dev>
On Fri, 2026-04-24 at 11:06 +0200, Thorsten Blum wrote:
> While the current code works correctly, replace unbounded sprintf()
> calls with the safer scnprintf() in hfsplus_lookup(), hfsplus_link(),
> and hfsplus_unlink() to follow secure coding best practices.
The patch makes sense. But I would like to request some refactoring work here.
:)
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> fs/hfsplus/dir.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/hfsplus/dir.c b/fs/hfsplus/dir.c
> index 47194370c2c5..ff976995ef58 100644
> --- a/fs/hfsplus/dir.c
> +++ b/fs/hfsplus/dir.c
> @@ -98,7 +98,7 @@ static struct dentry *hfsplus_lookup(struct inode *dir, struct dentry *dentry,
> dentry->d_fsdata = (void *)(unsigned long)cnid;
> linkid =
> be32_to_cpu(entry.file.permissions.dev);
> - str.len = sprintf(name, "iNode%d", linkid);
> + str.len = scnprintf(name, sizeof(name), "iNode%d", linkid);
> str.name = name;
> err = hfsplus_cat_build_key(sb, fd.search_key,
> HFSPLUS_SB(sb)->hidden_dir->i_ino,
This piece of code looks like a static inline function. Could we rework this
piece of code?
char name[32];
This declaration looks not very well. I think we need to introduce some named
constant for hardcoded 32 value. Could you please rework it?
> @@ -322,7 +322,7 @@ static int hfsplus_link(struct dentry *src_dentry, struct inode *dst_dir,
> get_random_bytes(&id, sizeof(cnid));
> id &= 0x3fffffff;
> str.name = name;
> - str.len = sprintf(name, "iNode%d", id);
> + str.len = scnprintf(name, sizeof(name), "iNode%d", id);
> res = hfsplus_rename_cat(inode->i_ino,
> src_dir, &src_dentry->d_name,
> sbi->hidden_dir, &str);
The same issue with name declaration here:
char name[32];
Also, I think it makes sense to initialize the local variables:
char name[32] = {0};
Maybe it makes sense to introduce some small function that execute this:
str.len = sprintf(name, "iNode%d", linkid);
str.name = name;
Something like this:
str = hfsplus_qstr_init(<arguments>);
What do you think?
> @@ -393,7 +393,7 @@ static int hfsplus_unlink(struct inode *dir, struct dentry *dentry)
> if (inode->i_ino == cnid &&
> atomic_read(&HFSPLUS_I(inode)->opencnt)) {
> str.name = name;
> - str.len = sprintf(name, "temp%llu", inode->i_ino);
> + str.len = scnprintf(name, sizeof(name), "temp%llu", inode->i_ino);
> res = hfsplus_rename_cat(inode->i_ino,
> dir, &dentry->d_name,
> sbi->hidden_dir, &str);
The same issues here too.
Thanks,
Slava.
[1] https://elixir.bootlin.com/linux/v7.0/source/fs/hfsplus/dir.c#L87
prev parent reply other threads:[~2026-04-24 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 9:06 [PATCH] hfsplus: replace unbounded sprintf() in hfsplus_{lookup,link,unlink} Thorsten Blum
2026-04-24 19:38 ` Viacheslav Dubeyko [this message]
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=a4d47cc47de0b887202fd73cb93bc02bff4095c8.camel@redhat.com \
--to=vdubeyko@redhat.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=thorsten.blum@linux.dev \
/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