From: Laurent Vivier <lvivier@redhat.com>
To: Jason Wang <jasowang@redhat.com>,
mst@redhat.com, mpm@selenic.com, herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+5b59d6d459306a556f54@syzkaller.appspotmail.com
Subject: Re: [PATCH] virtio-rng: make device ready before making request
Date: Wed, 8 Jun 2022 14:17:43 +0200 [thread overview]
Message-ID: <8733913f-b04b-f2c7-d7e2-d22740ab99af@redhat.com> (raw)
In-Reply-To: <20220608061422.38437-1-jasowang@redhat.com>
On 08/06/2022 08:14, Jason Wang wrote:
> Current virtio-rng does a entropy request before DRIVER_OK, this
> violates the spec and kernel will ignore the interrupt after commit
> 8b4ec69d7e09 ("virtio: harden vring IRQ").
>
> Fixing this by making device ready before the request.
>
> Fixes: 8b4ec69d7e09 ("virtio: harden vring IRQ")
> Reported-and-tested-by: syzbot+5b59d6d459306a556f54@syzkaller.appspotmail.com
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> drivers/char/hw_random/virtio-rng.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/char/hw_random/virtio-rng.c b/drivers/char/hw_random/virtio-rng.c
> index e856df7e285c..a6f3a8a2aca6 100644
> --- a/drivers/char/hw_random/virtio-rng.c
> +++ b/drivers/char/hw_random/virtio-rng.c
> @@ -159,6 +159,8 @@ static int probe_common(struct virtio_device *vdev)
> goto err_find;
> }
>
> + virtio_device_ready(vdev);
> +
> /* we always have a pending entropy request */
> request_entropy(vi);
>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
prev parent reply other threads:[~2022-06-08 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 6:14 [PATCH] virtio-rng: make device ready before making request Jason Wang
2022-06-08 12:17 ` 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=8733913f-b04b-f2c7-d7e2-d22740ab99af@redhat.com \
--to=lvivier@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=mst@redhat.com \
--cc=syzbot+5b59d6d459306a556f54@syzkaller.appspotmail.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