From: Mark McLoughlin <markmc@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: avi@redhat.com, kvm@vger.kernel.org,
Jens Osterkamp <Jens.Osterkamp@gmx.de>
Subject: Re: [PATCH 1/1] net: fix vnet_hdr bustage with slirp
Date: Fri, 07 Aug 2009 13:19:19 +0100 [thread overview]
Message-ID: <1249647559.3260.17.camel@blaa> (raw)
In-Reply-To: <200908071351.02086.arnd@arndb.de>
On Fri, 2009-08-07 at 13:51 +0200, Arnd Bergmann wrote:
> On Friday 07 August 2009, Mark McLoughlin wrote:
> > slirp has started using VLANClientState::opaque and this has caused the
> > kvm specific tap_has_vnet_hdr() hack to break because we blindly use
> > this opaque pointer even if it is not a tap client.
> >
> > Add yet another hack to check that we're actually getting called with a
> > tap client.
> >
> > [Needed on stable-0.11 too]
> >
> > Signed-off-by: Mark McLoughlin <markmc@redhat.com>
>
> Jens and I discovered the same bug before, but then we forgot about
> sending a fix (sorry). Your patch should work fine as a workaround,
> but I wonder if it is the right solution.
>
> The abstraction of struct VLANClientState is otherwise done through
> function pointers taking the VLANClientState pointer as their
> first argument. IMHO a cleaner abstraction would be to do the same
> for tap_has_vnet_hdr(), like the patch below, and similar for
> other functions passing 'opaque' pointers.
Indeed, but using vc->vlan->first_client is a great big hole in the
abstraction as it is.
The vnet_hdr code in qemu-kvm.git is a hack which we plan to
(eventually) replace by allowing a nic to be paired directly with a
backend.
Your patch is fine, but I'd suggest since both are a hack we stick with
mine since it'll reduce merge conflicts. Both hacks will go away
eventually, anyway.
Thanks,
Mark.
next prev parent reply other threads:[~2009-08-07 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 8:47 [PATCH 1/1] net: fix vnet_hdr bustage with slirp Mark McLoughlin
2009-08-07 11:51 ` Arnd Bergmann
2009-08-07 12:19 ` Mark McLoughlin [this message]
2009-08-07 13:20 ` Arnd Bergmann
2009-08-09 9:53 ` Avi Kivity
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=1249647559.3260.17.camel@blaa \
--to=markmc@redhat.com \
--cc=Jens.Osterkamp@gmx.de \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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 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.