From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Delete IOHandlers after potentially running them
Date: Wed, 03 Nov 2010 10:00:37 -0500 [thread overview]
Message-ID: <4CD17915.90104@codemonkey.ws> (raw)
In-Reply-To: <1288794584-6099-1-git-send-email-stefanha@linux.vnet.ibm.com>
On 11/03/2010 09:29 AM, Stefan Hajnoczi wrote:
> Since commit 4bed9837309e58d208183f81d8344996744292cf an .fd_read()
> handler that deletes its IOHandler is exposed to .fd_write() being
> called on the deleted IOHandler.
>
> This patch fixes deletion so that .fd_read() and .fd_write() are never
> called on an IOHandler that is marked for deletion.
>
> Signed-off-by: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
> ---
> vl.c | 15 ++++++++-------
> 1 files changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index 7038952..6f56123 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -1252,17 +1252,18 @@ void main_loop_wait(int nonblocking)
> IOHandlerRecord *pioh;
>
> QLIST_FOREACH_SAFE(ioh,&io_handlers, next, pioh) {
> - if (ioh->deleted) {
> - QLIST_REMOVE(ioh, next);
> - qemu_free(ioh);
> - continue;
> - }
> - if (ioh->fd_read&& FD_ISSET(ioh->fd,&rfds)) {
> + if (!ioh->deleted&& ioh->fd_read&& FD_ISSET(ioh->fd,&rfds)) {
> ioh->fd_read(ioh->opaque);
> }
> - if (ioh->fd_write&& FD_ISSET(ioh->fd,&wfds)) {
> + if (!ioh->deleted&& ioh->fd_write&& FD_ISSET(ioh->fd,&wfds)) {
> ioh->fd_write(ioh->opaque);
> }
> +
> + /* Do this last in case read/write handlers marked it for deletion */
> + if (ioh->deleted) {
> + QLIST_REMOVE(ioh, next);
> + qemu_free(ioh);
> + }
>
Actually, on second thought, I think this is correct although I still
think reverting is a better strategy.
Regards,
Anthony Liguori
> }
> }
>
>
next prev parent reply other threads:[~2010-11-03 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 14:29 [Qemu-devel] [PATCH] Delete IOHandlers after potentially running them Stefan Hajnoczi
2010-11-03 14:39 ` [Qemu-devel] " Juan Quintela
2010-11-03 14:40 ` Stefan Hajnoczi
2010-11-03 14:57 ` [Qemu-devel] " Anthony Liguori
2010-11-03 15:12 ` [Qemu-devel] " Juan Quintela
2010-11-03 17:43 ` Anthony Liguori
2010-11-03 18:39 ` Juan Quintela
2010-11-09 11:32 ` Stefan Hajnoczi
2010-11-03 15:00 ` Anthony Liguori [this message]
2010-11-16 22:24 ` [Qemu-devel] " Anthony Liguori
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=4CD17915.90104@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.