From: Laurent Vivier <lvivier@redhat.com>
To: Thorsten Blum <blum@kernel.org>,
Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: virtualization@lists.linux.dev, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] hwrng: virtio - use snprintf() in probe_common()
Date: Mon, 28 Sep 2026 08:31:24 +0200 [thread overview]
Message-ID: <f49cbe7d-79b1-44a3-bc26-9182284a74d6@redhat.com> (raw)
In-Reply-To: <20260926055853.4868-4-blum@kernel.org>
On 9/26/26 07:58, Thorsten Blum wrote:
> While the current code works correctly, replace the unbounded sprintf()
> with the safer snprintf() to follow secure coding best practices.
>
> Signed-off-by: Thorsten Blum <blum@kernel.org>
> ---
> drivers/char/hw_random/virtio-rng.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/hw_random/virtio-rng.c b/drivers/char/hw_random/virtio-rng.c
> index 5b1b23b5596a..f9982217247d 100644
> --- a/drivers/char/hw_random/virtio-rng.c
> +++ b/drivers/char/hw_random/virtio-rng.c
> @@ -162,7 +162,7 @@ static int probe_common(struct virtio_device *vdev)
> err = index;
> goto err_ida;
> }
> - sprintf(vi->name, "virtio_rng.%d", index);
> + snprintf(vi->name, sizeof(vi->name), "virtio_rng.%d", vi->index);
> init_completion(&vi->have_data);
>
> vi->hwrng = (struct hwrng) {
>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
prev parent reply other threads:[~2026-09-28 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 5:58 [PATCH 1/2] hwrng: virtio - use min() in copy_data() Thorsten Blum
2026-09-26 5:58 ` [PATCH 2/2] hwrng: virtio - use snprintf() in probe_common() Thorsten Blum
2026-09-28 6:24 ` Thomas Huth
2026-09-28 6:31 ` Laurent Vivier [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=f49cbe7d-79b1-44a3-bc26-9182284a74d6@redhat.com \
--to=lvivier@redhat.com \
--cc=blum@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivia@selenic.com \
--cc=virtualization@lists.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
all inboxes | Powered by JetHome®