From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH] mmc: mmc_spi: fix snprintf() output buffer size
Date: Mon, 7 Oct 2024 20:09:14 +0200 [thread overview]
Message-ID: <ab1180ff-b435-46c8-82a8-66fea41db110@wanadoo.fr> (raw)
In-Reply-To: <20241007114549.51213-1-brgl@bgdev.pl>
Le 07/10/2024 à 13:45, Bartosz Golaszewski a écrit :
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> GCC 13 complains about the truncated output of snprintf():
>
> drivers/mmc/host/mmc_spi.c: In function ‘mmc_spi_response_get’:
> drivers/mmc/host/mmc_spi.c:227:64: error: ‘snprintf’ output may be truncated before the last format character [-Werror=format-truncation=]
> 227 | snprintf(tag, sizeof(tag), " ... CMD%d response SPI_%s",
> | ^
> drivers/mmc/host/mmc_spi.c:227:9: note: ‘snprintf’ output between 26 and 43 bytes into a destination of size 32
> 227 | snprintf(tag, sizeof(tag), " ... CMD%d response SPI_%s",
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 228 | cmd->opcode, maptype(cmd));
>
> Increase the size of the target buffer.
>
> Fixes: 15a0580ced08 ("mmc_spi host driver")
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> drivers/mmc/host/mmc_spi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/mmc_spi.c b/drivers/mmc/host/mmc_spi.c
> index 8fee7052f2ef..fa1d1a1b3142 100644
> --- a/drivers/mmc/host/mmc_spi.c
> +++ b/drivers/mmc/host/mmc_spi.c
> @@ -222,7 +222,7 @@ static int mmc_spi_response_get(struct mmc_spi_host *host,
> u8 leftover = 0;
> unsigned short rotator;
> int i;
> - char tag[32];
> + char tag[43];
>
> snprintf(tag, sizeof(tag), " ... CMD%d response SPI_%s",
> cmd->opcode, maptype(cmd));
'tag' is only used in a dev_dbg() at the end of the function.
Maybe " ... CMD%d response SPI_%s" could me moved directly within the
dev_dbg(). This would save a few bytes on the stack, save a snprintf()
in the normal path and fix the warning without the need of magic number.
just my 2c.
CJ
next prev parent reply other threads:[~2024-10-07 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 11:45 [PATCH] mmc: mmc_spi: fix snprintf() output buffer size Bartosz Golaszewski
2024-10-07 18:09 ` Christophe JAILLET [this message]
2024-10-08 7:13 ` Bartosz Golaszewski
2024-10-08 14:16 ` Ulf Hansson
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=ab1180ff-b435-46c8-82a8-66fea41db110@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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