From: Alexey Dobriyan <adobriyan@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Alexey Dobriyan <adobriyan@yandex-team.ru>,
qemu-devel@nongnu.org, mst@redhat.com, vsementsov@yandex-team.ru
Subject: Re: [PATCH 1/1] virtio-net: fix bug 1451 aka "assert(!virtio_net_get_subqueue(nc)->async_tx.elem);"
Date: Tue, 9 Apr 2024 09:01:23 +0300 [thread overview]
Message-ID: <f5628612-9cc2-4ff1-8a36-a26830c9f098@p183> (raw)
In-Reply-To: <CACGkMEv-znr-sSXLHmBvcrLMDyrT739tqRQkcQbzLc4XPyU4ZQ@mail.gmail.com>
On Mon, Apr 08, 2024 at 03:26:35PM +0800, Jason Wang wrote:
> On Fri, Apr 5, 2024 at 7:22 PM Alexey Dobriyan <adobriyan@yandex-team.ru> wrote:
> >
> > Don't send zero length packets in virtio_net_flush_tx().
> >
> > Reproducer from https://gitlab.com/qemu-project/qemu/-/issues/1451
> > creates small packet (1 segment, len = 10 == n->guest_hdr_len),
> > destroys queue.
> >
> > "if (n->host_hdr_len != n->guest_hdr_len)" is triggered, if body creates
> > zero length/zero segment packet, because there is nothing after guest
> > header.
>
> And in this case host_hdr_len is 0.
Yes.
> > qemu_sendv_packet_async() tries to send it.
> >
> > slirp discards it because it is smaller than Ethernet header,
> > but returns 0.
> >
> > 0 length is propagated upwards and is interpreted as "packet has been sent"
> > which is terrible because queue is being destroyed, nothing has been sent,
> > nobody is waiting for TX to complete and assert it triggered.
> > @@ -2807,6 +2803,11 @@ static int32_t virtio_net_flush_tx(VirtIONetQueue *q)
> > n->guest_hdr_len, -1);
> > out_num = sg_num;
> > out_sg = sg;
> > +
> > + if (iov_size(out_sg, out_num) == 0) {
> > + virtio_error(vdev, "virtio-net nothing to send");
> > + goto detach;
> > + }
>
> Nit, I think we can do this check before the iov_copy()?
I'd rather check for "badness" right before emitting packet.
> > }
> >
> > ret = qemu_sendv_packet_async(qemu_get_subqueue(n->nic, queue_index),
> > @@ -2827,6 +2828,11 @@ drop:
> > }
> > }
> > return num_packets;
> > +
> > +detach:
> > + virtqueue_detach_element(q->tx_vq, elem, 0);
> > + g_free(elem);
> > + return -EINVAL;
> > }
> >
> > static void virtio_net_tx_timer(void *opaque);
> > --
> > 2.34.1
> >
>
next prev parent reply other threads:[~2024-04-09 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 11:20 [PATCH 1/1] virtio-net: fix bug 1451 aka "assert(!virtio_net_get_subqueue(nc)->async_tx.elem); " Alexey Dobriyan
2024-04-08 7:26 ` Jason Wang
2024-04-09 6:01 ` Alexey Dobriyan [this message]
2024-04-09 6:49 ` [PATCH 1/1] virtio-net: fix bug 1451 aka "assert(!virtio_net_get_subqueue(nc)->async_tx.elem);" Michael S. Tsirkin
2024-04-09 6:51 ` Michael S. Tsirkin
2024-04-09 16:37 ` Alexey Dobriyan
2024-04-09 16:41 ` Michael S. Tsirkin
2024-04-09 17:15 ` Alexey Dobriyan
-- strict thread matches above, loose matches on Subject: below --
2024-04-09 19:05 [PATCH 1/1] virtio-net: fix bug 1451 aka "assert(!virtio_net_get_subqueue(nc)->async_tx.elem); " Alexey Dobriyan
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=f5628612-9cc2-4ff1-8a36-a26830c9f098@p183 \
--to=adobriyan@gmail.com \
--cc=adobriyan@yandex-team.ru \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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).