qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: s.priebe@profihost.ag, pbonzini@redhat.com,
	qemu-stable@nongnu.org, hongyang.yang@easystack.cn
Subject: Re: [Qemu-devel] [PATCH V3] net: fix qemu_announce_self not emitting packets
Date: Mon, 13 Jun 2016 10:56:18 +0800	[thread overview]
Message-ID: <575E20D2.30406@redhat.com> (raw)
In-Reply-To: <1465465167-4698-1-git-send-email-pl@kamp.de>



On 2016年06月09日 17:39, Peter Lieven wrote:
> commit fefe2a78 accidently dropped the code path for injecting
> raw packets. This feature is needed for sending gratuitous ARPs
> after an incoming migration has completed. The result is increased
> network downtime for vservers where the network card is not virtio-net
> with the VIRTIO_NET_F_GUEST_ANNOUNCE feature.
>
> Fixes: fefe2a78abde932e0f340b21bded2c86def1d242
> Cc: qemu-stable@nongnu.org
> Cc: hongyang.yang@easystack.cn
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> v1->v2: assert that only raw packets with a plain buffer come in. [Paolo]
> v2->v3: nc_senv_compat can take care of raw packets [Paolo, Jason]
>
>   net/net.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/net.c b/net/net.c
> index 5f3e5a9..75bb177 100644
> --- a/net/net.c
> +++ b/net/net.c
> @@ -722,7 +722,7 @@ ssize_t qemu_deliver_packet_iov(NetClientState *sender,
>           return 0;
>       }
>   
> -    if (nc->info->receive_iov) {
> +    if (nc->info->receive_iov && !(flags & QEMU_NET_PACKET_FLAG_RAW)) {
>           ret = nc->info->receive_iov(nc, iov, iovcnt);
>       } else {
>           ret = nc_sendv_compat(nc, iov, iovcnt, flags);

Applied to -net. Thanks

      reply	other threads:[~2016-06-13  2:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09  9:39 [Qemu-devel] [PATCH V3] net: fix qemu_announce_self not emitting packets Peter Lieven
2016-06-13  2:56 ` 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=575E20D2.30406@redhat.com \
    --to=jasowang@redhat.com \
    --cc=hongyang.yang@easystack.cn \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=s.priebe@profihost.ag \
    /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).