From: Amit Shah <amit.shah@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: kvm@vger.kernel.org, stable@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio-rng: complete have_data completion in removing device
Date: Wed, 6 Aug 2014 13:55:29 +0530 [thread overview]
Message-ID: <20140806082529.GC25951@grmbl.mre> (raw)
In-Reply-To: <20140806080541.GA3304@z.redhat.com>
On (Wed) 06 Aug 2014 [16:05:41], Amos Kong wrote:
> On Wed, Aug 06, 2014 at 01:35:15AM +0800, Amos Kong wrote:
> > 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.
>
> 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-unplug on the succeeding wait, the value in data_avail
will be re-used, and the hwrng core will wrongly take some bytes in
the buffer as input from the host.
So, I think we need to set vi->data_avail = 0; before calling
wait_event_completion_killable().
Amit
next prev parent reply other threads:[~2014-08-06 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 17:35 [PATCH] virtio-rng: complete have_data completion in removing device Amos Kong
2014-08-06 8:05 ` Amos Kong
2014-08-06 8:25 ` Amit Shah [this message]
2014-09-08 15:29 ` Amos Kong
2014-09-09 10:47 ` Amos Kong
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=20140806082529.GC25951@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=akong@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).