From: sashiko-bot@kernel.org
To: "Oleg Drokin" <green@linuxhacker.ru>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH net 1/3] vhost/vsock: release the accounting of packets dropped on rx errors
Date: Fri, 06 Nov 2026 00:02:17 +0000 [thread overview]
Message-ID: <sashiko-outbox-200419@kernel.org> (raw)
In-Reply-To: <20261105000141.3617241-2-green@linuxhacker.ru>
> When vhost_transport_do_send_pkt() fails to deliver a packet to the guest
> (unexpected output buffers, a buffer smaller than the header, a fault
> while copying the header or the payload) it frees the skb with
> kfree_skb() and gives up. The success path does more:
> virtio_transport_consume_skb_sent() subtracts the payload from the
> socket's bytes_unsent (SIOCOUTQ), and for a reply the queued_replies
> counter is decremented, restarting the guest's tx queue once it drops
> below the ring size.
>
> The error paths skip both. Every such drop leaves SIOCOUTQ too high for
> the life of the socket, and every dropped reply permanently takes one
> slot of the queued_replies budget, so that after a ring's worth of them
> vhost stops processing the guest's tx queue for good.
>
> Release both on the error paths, as the success path does.
>
> Fixes: 433fc58e6bf2 ("VSOCK: Introduce vhost_vsock.ko")
> Fixes: e6ab45005772 ("vsock/virtio: add SIOCOUTQ support for all virtio based transports")
> Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105000141.3617241-1-green@linuxhacker.ru?part=1
next prev parent reply other threads:[~2026-11-06 0:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 0:01 [PATCH net 0/3] vsock/virtio: bound what a peer can make the host queue Oleg Drokin
2026-11-05 0:01 ` [PATCH net 1/3] vhost/vsock: release the accounting of packets dropped on rx errors Oleg Drokin
2026-11-06 0:02 ` sashiko-bot [this message]
2026-11-05 0:01 ` [PATCH net 2/3] vsock/virtio: bound the send credit by bytes not yet consumed by the transport Oleg Drokin
2026-11-06 0:02 ` sashiko-bot
2026-11-05 0:01 ` [PATCH net 3/3] vsock/virtio: queue at most one credit update per socket Oleg Drokin
2026-11-06 0:02 ` sashiko-bot
2026-11-06 0:19 ` Michael S. Tsirkin
2026-11-06 5:02 ` Oleg Drokin
2026-11-09 0:36 ` netdev-bot+sashiko
2026-11-05 0:03 ` [PATCH net 0/3] vsock/virtio: bound what a peer can make the host queue netdev-bot+sinfo
2026-11-05 0:19 ` Oleg Drokin
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=sashiko-outbox-200419@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=green@linuxhacker.ru \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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