From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: jasowang@redhat.com, yanghy@cn.fujitsu.com,
qemu-stable@nongnu.org, s.priebe@profihost.ag
Subject: Re: [Qemu-devel] [PATCH] net: fix qemu_announce_self not emitting packets
Date: Tue, 7 Jun 2016 10:23:09 +0200 [thread overview]
Message-ID: <f14fb383-ec70-71d2-c1e0-25a887b1d360@redhat.com> (raw)
In-Reply-To: <57567FAD.803@kamp.de>
On 07/06/2016 10:02, Peter Lieven wrote:
> Am 07.06.2016 um 09:55 schrieb Paolo Bonzini:
>>
>> On 07/06/2016 09:37, 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: yanghy@cn.fujitsu.com
>>> Signed-off-by: Peter Lieven <pl@kamp.de>
>>> ---
>>> net/net.c | 6 +++++-
>>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/net/net.c b/net/net.c
>>> index 5f3e5a9..d5834ea 100644
>>> --- a/net/net.c
>>> +++ b/net/net.c
>>> @@ -722,7 +722,11 @@ ssize_t qemu_deliver_packet_iov(NetClientState
>>> *sender,
>>> return 0;
>>> }
>>> - if (nc->info->receive_iov) {
>>> + if (flags & QEMU_NET_PACKET_FLAG_RAW && iovcnt == 1 &&
>>> + nc->info->receive_raw) {
>>> + /* this is required for qemu_announce_self() */
>>> + ret = nc->info->receive_raw(nc, iov[0].iov_base,
>>> iov[0].iov_len);
>> Possibly move "iovcnt == 1" from the if condition to an assertion
>> inside it?
>
> I do not know if there is any other user that emits raw packets than
> qemu_announce_self.
Currently all senders of raw packets go through qemu_send_packet_raw,
which has iovcnt == 1.
> The question is do you want to abort or just return -1 (which is the
> case without this patch).
I want to abort, since it's currently impossible to get into that
situation. If someone wants to introduce
qemu_sendv_packet_async_with_flags, they must also introduce
nc->info->receive_raw_iov or something like that.
Thanks,
Paolo
next prev parent reply other threads:[~2016-06-07 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 7:37 [Qemu-devel] [PATCH] net: fix qemu_announce_self not emitting packets Peter Lieven
2016-06-07 7:55 ` Paolo Bonzini
2016-06-07 8:02 ` Peter Lieven
2016-06-07 8:23 ` Paolo Bonzini [this message]
2016-06-07 9:33 ` Stefan Priebe - Profihost AG
2016-06-07 11:35 ` Yang Hongyang
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=f14fb383-ec70-71d2-c1e0-25a887b1d360@redhat.com \
--to=pbonzini@redhat.com \
--cc=jasowang@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=s.priebe@profihost.ag \
--cc=yanghy@cn.fujitsu.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 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).