From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] remoteproc: mtk_scp: change the snprintf() checking
Date: Mon, 10 Nov 2025 10:43:41 -0700 [thread overview]
Message-ID: <aRIkTV8C9gjSyH-o@p14s> (raw)
In-Reply-To: <aP8agyKj73bLZrTQ@stanley.mountain>
On Mon, Oct 27, 2025 at 10:08:51AM +0300, Dan Carpenter wrote:
> The snprintf() calls here work but they have several minor style issues:
>
> 1) It uses ARRAY_SIZE() which is the number of elements in an array.
> Since were talking about char that works, but it's more common to
> use sizeof() which is the number of bytes.
> 2) The printf format is "%1d". The "1" ensures we always print at
> least 1 character but since numbers all have at least 1 digit this
> can be removed.
> 3) The kernel implementation of snprintf() cannot return negative error
> codes. Also these particular calls to snprintf() can't return zero
> and the code to handle that zero return is sort of questionable.
> 4) In the current kernel the only "core_id" we print is "0" but if it
> was more than 9 then the output would be truncated so GCC complains.
> Add an "a >= sizeof(scp_fw_file)" check for output which is too long.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> v2: The v1 introduced a W=1 warning because of the truncation issue.
> It's a false positive because GCC assumes that "core_id" can be
> every possible value of int but actually it can only be zero. And
> also generally, in the kernel, truncating is fine and it is fine
> here too.
>
> But let's use that as an opportunity to do more cleanups.
>
> drivers/remoteproc/mtk_scp.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c
> index 10e3f9eb8cd2..db8fd045468d 100644
> --- a/drivers/remoteproc/mtk_scp.c
> +++ b/drivers/remoteproc/mtk_scp.c
> @@ -1127,11 +1127,11 @@ static const char *scp_get_default_fw_path(struct device *dev, int core_id)
> return ERR_PTR(-EINVAL);
>
> if (core_id >= 0)
> - ret = snprintf(scp_fw_file, ARRAY_SIZE(scp_fw_file), "scp_c%1d", core_id);
> + ret = snprintf(scp_fw_file, sizeof(scp_fw_file), "scp_c%d", core_id);
> else
> - ret = snprintf(scp_fw_file, ARRAY_SIZE(scp_fw_file), "scp");
> - if (ret <= 0)
> - return ERR_PTR(ret);
> + ret = snprintf(scp_fw_file, sizeof(scp_fw_file), "scp");
> + if (ret >= sizeof(scp_fw_file))
> + return ERR_PTR(-ENAMETOOLONG);
>
Applied.
Thanks,
Mathieu
> /* Not using strchr here, as strlen of a const gets optimized by compiler */
> soc = &compatible[strlen("mediatek,")];
> --
> 2.51.0
>
prev parent reply other threads:[~2025-11-10 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 7:08 [PATCH v2] remoteproc: mtk_scp: change the snprintf() checking Dan Carpenter
2025-10-27 9:32 ` AngeloGioacchino Del Regno
2025-10-27 11:55 ` Zhongqiu Han
2025-11-10 17:43 ` Mathieu Poirier [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=aRIkTV8C9gjSyH-o@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dan.carpenter@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
/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).