From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org, Amit Shah <amit@kernel.org>
Subject: Re: [PATCH] virtio-rng: block max-bytes=0
Date: Tue, 30 Jul 2024 07:29:17 -0400 [thread overview]
Message-ID: <20240730072753-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f6beb6d6-5434-4f85-a00b-20d662b77b36@redhat.com>
On Tue, Jul 30, 2024 at 11:07:11AM +0200, Laurent Vivier wrote:
> On 24/07/2024 12:51, Michael S. Tsirkin wrote:
> > with max-bytes set to 0, quota is 0 and so device does not work.
> > block this to avoid user confusion
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > hw/virtio/virtio-rng.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/virtio/virtio-rng.c b/hw/virtio/virtio-rng.c
> > index f74efffef7..7cf31da071 100644
> > --- a/hw/virtio/virtio-rng.c
> > +++ b/hw/virtio/virtio-rng.c
> > @@ -184,8 +184,9 @@ static void virtio_rng_device_realize(DeviceState *dev, Error **errp)
> > /* Workaround: Property parsing does not enforce unsigned integers,
> > * So this is a hack to reject such numbers. */
> > - if (vrng->conf.max_bytes > INT64_MAX) {
> > - error_setg(errp, "'max-bytes' parameter must be non-negative, "
> > + if (vrng->conf.max_bytes == 0 ||
> > + vrng->conf.max_bytes > INT64_MAX) {
> > + error_setg(errp, "'max-bytes' parameter must be positive, "
> > "and less than 2^63");
> > return;
> > }
>
> Michael, do you plan to send the PR yourself? Or perhaps it can go via trivial?
>
> Thanks,
> Laurent
I will pick it up, I do not think this is appropriate for trivial though.
--
MST
prev parent reply other threads:[~2024-07-30 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 10:51 [PATCH] virtio-rng: block max-bytes=0 Michael S. Tsirkin
2024-07-24 11:06 ` Laurent Vivier
2024-07-24 12:30 ` Amit Shah
2024-07-25 7:05 ` Philippe Mathieu-Daudé
2024-07-30 9:07 ` Laurent Vivier
2024-07-30 11:29 ` Michael S. Tsirkin [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=20240730072753-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=amit@kernel.org \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).