Displaying 6 results from an estimated 6 matches for "rng_get_date".
Did you mean:
rng_get_data
2014 Aug 05
2
[PATCH] virtio-rng: complete have_data completion in removing device
When we try to hot-remove a busy virtio-rng device from QEMU monitor,
the device can't be hot-removed. Because virtio-rng driver hangs at
wait_for_completion_killable().
This patch fixed the hang by completing have_data completion before
unregistering a virtio-rng device.
Signed-off-by: Amos Kong <akong at redhat.com>
Cc: stable at vger.kernel.org
---
2014 Aug 05
2
[PATCH] virtio-rng: complete have_data completion in removing device
When we try to hot-remove a busy virtio-rng device from QEMU monitor,
the device can't be hot-removed. Because virtio-rng driver hangs at
wait_for_completion_killable().
This patch fixed the hang by completing have_data completion before
unregistering a virtio-rng device.
Signed-off-by: Amos Kong <akong at redhat.com>
Cc: stable at vger.kernel.org
---
2014 Aug 06
2
[PATCH] virtio-rng: complete have_data completion in removing device
...before
> > unregistering a virtio-rng device.
>
> Hi Amit,
>
> Before applying this patch, it's blocking insider wait_for_completion_killable()
> Applied this patch, wait_for_completion_killable() returns 0,
> and vi->data_avail becomes 0, then rng_get_date() will return 0.
Thanks for checking this.
> Is it expected result?
I think what will happen is vi->data_avail will be set to whatever it
was set last. In case of a previous successful read request, the
data_avail will be set to whatever number of bytes the host gave. On
doing a hot-unpl...
2014 Aug 06
2
[PATCH] virtio-rng: complete have_data completion in removing device
...before
> > unregistering a virtio-rng device.
>
> Hi Amit,
>
> Before applying this patch, it's blocking insider wait_for_completion_killable()
> Applied this patch, wait_for_completion_killable() returns 0,
> and vi->data_avail becomes 0, then rng_get_date() will return 0.
Thanks for checking this.
> Is it expected result?
I think what will happen is vi->data_avail will be set to whatever it
was set last. In case of a previous successful read request, the
data_avail will be set to whatever number of bytes the host gave. On
doing a hot-unpl...
2014 Aug 06
0
[PATCH] virtio-rng: complete have_data completion in removing device
...by completing have_data completion before
> unregistering a virtio-rng device.
Hi Amit,
Before applying this patch, it's blocking insider wait_for_completion_killable()
Applied this patch, wait_for_completion_killable() returns 0,
and vi->data_avail becomes 0, then rng_get_date() will return 0.
Is it expected result?
> Signed-off-by: Amos Kong <akong at redhat.com>
> Cc: stable at vger.kernel.org
> ---
> drivers/char/hw_random/virtio-rng.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/char/hw_random/virtio-rng.c b/driver...
2014 Sep 08
0
[PATCH] virtio-rng: complete have_data completion in removing device
...g a virtio-rng device.
> >
> > Hi Amit,
> >
> > Before applying this patch, it's blocking insider wait_for_completion_killable()
> > Applied this patch, wait_for_completion_killable() returns 0,
> > and vi->data_avail becomes 0, then rng_get_date() will return 0.
>
> Thanks for checking this.
>
> > Is it expected result?
>
> I think what will happen is vi->data_avail will be set to whatever it
> was set last. In case of a previous successful read request, the
> data_avail will be set to whatever number of b...