From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sun Jian <sun.jian.kdev@gmail.com>
Cc: Vaibhav Agarwal <vaibhav.sr@gmail.com>,
Johan Hovold <johan@kernel.org>,
Mark Greer <mgreer@animalcreek.com>,
Alex Elder <elder@kernel.org>,
David Laight <david.laight.linux@gmail.com>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: greybus: audio: avoid snprintf truncation warnings
Date: Tue, 30 Dec 2025 08:40:48 +0100 [thread overview]
Message-ID: <2025123028-transform-nutshell-81fa@gregkh> (raw)
In-Reply-To: <20251230012908.214959-1-sun.jian.kdev@gmail.com>
On Tue, Dec 30, 2025 at 09:29:08AM +0800, Sun Jian wrote:
> W=1 reports possible truncation when formatting widget/control names
> with snprintf() and a %s argument. Use a small helper and hide the %s
> pointer from the compiler's truncation analysis via OPTIMIZER_HIDE_VAR(),
> while keeping the existing snprintf() formatting.
>
> No functional change intended.
>
> Signed-off-by: Sun Jian <sun.jian.kdev@gmail.com>
>
> Changes in v3:
> - Replace the earlier scnprintf()/strlcat() approach with a helper
> keeping snprintf().
> - Hide the %s argument from compiler truncation analysis using
> OPTIMIZER_HIDE_VAR().
> - Add a small local length limit macro with a short comment.
> ---
The "changes" go below the --- line, as the documentation asks for. And
please include what changed from versions prior to that as well.
But:
> drivers/staging/greybus/audio_topology.c | 22 +++++++++++++++-------
> 1 file changed, 15 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/staging/greybus/audio_topology.c b/drivers/staging/greybus/audio_topology.c
> index 76146f91cddc..35775067897c 100644
> --- a/drivers/staging/greybus/audio_topology.c
> +++ b/drivers/staging/greybus/audio_topology.c
> @@ -1009,6 +1009,19 @@ static const struct snd_soc_dapm_widget gbaudio_widgets[] = {
> SND_SOC_DAPM_POST_PMD),
> };
>
> +/* Limit %s length to avoid -Wformat-truncation with snprintf() */
> +#define GB_NAME_TMP_LEN 32
> +
> +static void gbaudio_prefix_dev_id(char *name, size_t name_len,
> + unsigned int dev_id)
> +{
> + char temp_name[GB_NAME_TMP_LEN], *cp = temp_name;
> +
> + strscpy(temp_name, name, sizeof(temp_name));
> + OPTIMIZER_HIDE_VAR(cp);
What? Why? That feels wrong. Let's not add hacks for broken
compilers.
> + snprintf(name, name_len, "GB %u %s", dev_id, cp);
> +}
> +
> static int gbaudio_tplg_create_widget(struct gbaudio_module_info *module,
> struct snd_soc_dapm_widget *dw,
> struct gb_audio_widget *w, int *w_size)
> @@ -1018,7 +1031,6 @@ static int gbaudio_tplg_create_widget(struct gbaudio_module_info *module,
> struct gb_audio_control *curr;
> struct gbaudio_control *control, *_control;
> size_t size;
> - char temp_name[NAME_SIZE];
>
> ret = gbaudio_validate_kcontrol_count(w);
> if (ret) {
> @@ -1086,8 +1098,7 @@ static int gbaudio_tplg_create_widget(struct gbaudio_module_info *module,
> }
>
> /* Prefix dev_id to widget control_name */
> - strscpy(temp_name, w->name, sizeof(temp_name));
> - snprintf(w->name, sizeof(w->name), "GB %d %s", module->dev_id, temp_name);
> + gbaudio_prefix_dev_id(w->name, sizeof(w->name), module->dev_id);
This feels like a broken tool, let's not do foolish things just to make
compilers quiet. W=1 is not a good reason to just make things "silent"
by moving code around like you did here.
sorry,
greg k-h
next prev parent reply other threads:[~2025-12-30 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 11:26 [PATCH] staging: greybus: audio: avoid snprintf truncation warnings Sun Jian
2025-12-29 14:17 ` David Laight
2025-12-29 16:13 ` [PATCH v2] " Sun Jian
2025-12-29 16:52 ` Greg Kroah-Hartman
2025-12-30 1:29 ` [PATCH v3] " Sun Jian
2025-12-30 7:40 ` Greg Kroah-Hartman [this message]
2025-12-30 22:20 ` David Laight
2026-01-05 11:55 ` Dan Carpenter
2026-01-05 15:37 ` sun jian
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=2025123028-transform-nutshell-81fa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=david.laight.linux@gmail.com \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mgreer@animalcreek.com \
--cc=sun.jian.kdev@gmail.com \
--cc=vaibhav.sr@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