From: Michal Privoznik <mprivozn@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, stefanha@redhat.com,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tap: properly initialize vhostfds
Date: Fri, 19 Apr 2013 13:24:35 +0200 [thread overview]
Message-ID: <51712973.3000003@redhat.com> (raw)
In-Reply-To: <1366355475-7243-1-git-send-email-jasowang@redhat.com>
On 19.04.2013 09:11, Jason Wang wrote:
> Only tap->vhostfd were checked net_init_tap_one(), but tap->vhostfds were
> forgot, this will lead qemu to ignore all fds passed by management through
> vhostfds, and tries to create vhost_net device itself. Fix by adding this check
> also.
>
> Reportyed-by: Michal Privoznik <mprivozn@redhat.com>
Typo
> Cc: Michal Privoznik <mprivozn@redhat.com>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> net/tap.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/net/tap.c b/net/tap.c
> index 17bdf01..e0b7a2a 100644
> --- a/net/tap.c
> +++ b/net/tap.c
> @@ -623,7 +623,7 @@ static int net_init_tap_one(const NetdevTapOptions *tap, NetClientState *peer,
> vhostfdname || (tap->has_vhostforce && tap->vhostforce)) {
> int vhostfd;
>
> - if (tap->has_vhostfd) {
> + if (tap->has_vhostfd || tap->has_vhostfds) {
> vhostfd = monitor_handle_fd_param(cur_mon, vhostfdname);
> if (vhostfd == -1) {
> return -1;
>
Yup. I can confirm this fixes the problem for me.
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
Michal
next prev parent reply other threads:[~2013-04-19 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 7:11 [Qemu-devel] [PATCH] tap: properly initialize vhostfds Jason Wang
2013-04-19 11:24 ` Michal Privoznik [this message]
2013-04-22 12:45 ` Stefan Hajnoczi
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=51712973.3000003@redhat.com \
--to=mprivozn@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.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.