qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] tap: clear vhost_net backend on cleanup
Date: Thu, 28 Oct 2010 15:40:47 +0800	[thread overview]
Message-ID: <19657.10495.746314.421330@gargle.gargle.HOWL> (raw)
In-Reply-To: <20101027180343.GA27426@redhat.com>

Michael S. Tsirkin writes:
 > Frontends calling tap_get_vhost_net get an invalid pointer after the
 > peer backend has been deleted. Jason Wang <jasowang@redhat.com> reports
 > this leading to a crash in ack_features when we remove the vhost-net
 > bakend of a virtio nic.
 > 
 > The fix is simply to clear the backend pointer.
 > 
 > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
 > ---
 > 
 > Jason, could you please confirm whether this patch
 > will fix the issue you have observed?
 > 
 > Thanks,
 > 

Yes it does, and how about also add assign fd to -1 in tap_cleanup()
and then check it in virtio_net_set_features() otherwise we could get
warning of the failure of offload setting?

 >  net/tap.c |    1 +
 >  1 files changed, 1 insertions(+), 0 deletions(-)
 > 
 > diff --git a/net/tap.c b/net/tap.c
 > index 0147dab..4cfa538 100644
 > --- a/net/tap.c
 > +++ b/net/tap.c
 > @@ -258,6 +258,7 @@ static void tap_cleanup(VLANClientState *nc)
 >  
 >      if (s->vhost_net) {
 >          vhost_net_cleanup(s->vhost_net);
 > +        s->vhost_net = NULL;
 >      }
 >  
 >      qemu_purge_queued_packets(nc);
 > -- 
 > 1.7.3.2.91.g446ac

      reply	other threads:[~2010-10-28  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 18:03 [Qemu-devel] [PATCH] tap: clear vhost_net backend on cleanup Michael S. Tsirkin
2010-10-28  7:40 ` Jason Wang [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=19657.10495.746314.421330@gargle.gargle.HOWL \
    --to=jasowang@redhat.com \
    --cc=mst@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).