From: Jason Wang <jasowang@redhat.com>
To: Greg Kurz <groug@kaod.org>, qemu-devel@nongnu.org
Cc: R Nageswara Sastry <nasastry@in.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] virtio_net: flush uncompleted TX on reset
Date: Tue, 20 Mar 2018 11:27:26 +0800 [thread overview]
Message-ID: <1301d99e-9cc8-e481-985e-4afe9bd6b82c@redhat.com> (raw)
In-Reply-To: <181e938f-76b7-84b2-96f1-1f8832236e23@redhat.com>
>> -static
>> void qemu_flush_or_purge_queued_packets(NetClientState *nc, bool
>> purge)
>> {
>> nc->receive_disabled = 0;
>>
>>
>
> Applied and queued for -stable.
>
> Thanks
>
Unfortunately, this breaks hotplug test:
TEST: tests/virtio-net-test... (pid=7117)
/x86_64/virtio/net/pci/basic: OK
/x86_64/virtio/net/pci/rx_stop_cont: OK
/x86_64/virtio/net/pci/hotplug: Broken pipe
FAIL
Thanks
next prev parent reply other threads:[~2018-03-20 3:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 12:07 [Qemu-devel] [PATCH v2] virtio_net: flush uncompleted TX on reset Greg Kurz
2018-03-20 2:34 ` Jason Wang
2018-03-20 3:27 ` Jason Wang [this message]
2018-03-20 10:20 ` Greg Kurz
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=1301d99e-9cc8-e481-985e-4afe9bd6b82c@redhat.com \
--to=jasowang@redhat.com \
--cc=groug@kaod.org \
--cc=mst@redhat.com \
--cc=nasastry@in.ibm.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).