public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] udp_vu: Discard datagrams when RX virtqueue is not usable
Date: Tue, 6 Jan 2026 08:48:31 +0100	[thread overview]
Message-ID: <92742f50-f095-45af-b43b-4d49254886f6@redhat.com> (raw)
In-Reply-To: <aVxJOjyY9kg6CN1m@zatzit>

On 1/6/26 00:28, David Gibson wrote:
> On Mon, Jan 05, 2026 at 03:50:16PM +0100, Laurent Vivier wrote:
>> During vhost-user device initialization, UDP datagrams may arrive on
>> listening sockets before the guest has enabled the RX virtqueue.
>>
>> When this happens, udp_vu_sock_recv() returns 0 without consuming
>> the datagram from the socket. The caller, udp_sock_fwd(), uses a
>> while loop with udp_peek_addr() to process pending datagrams. Since
>> the datagram remains in the socket buffer, udp_peek_addr() keeps
>> returning data available, causing a busy loop with 100% CPU usage.
>>
>> Add an early check for virtqueue readiness in udp_vu_sock_to_tap(),
>> mirroring tcp_vu_data_from_sock(). When the queue is not enabled or
>> not started, explicitly discard the datagram with recvmsg() and
>> return. The caller will drain remaining datagrams through repeated
>> calls.
>>
>> Fixes: 28997fcb29b5 ("vhost-user: add vhost-user")
>> Link: https://bugs.passt.top/show_bug.cgi?id=185
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> 
> My only concern here is that this will only consume a single datagram,
> whereas it looks like the loop could consume multiple datagrams.  I'm
> guessing something higher up will keep calling this until the queue is
> empty, but I'm not certain.  Otherwise LGTM.

I can move the change into udp_vu_sock_recv() (inside the datagram loop), it will be 
closer to what udp_buf_sock_to_tap() does: reads data with udp_sock_recv() and if fd_tap 
is not initialized tap_send_frames() drops them.

Thanks,
Laurent
>> ---
>>   udp_vu.c | 11 +++++++++++
>>   1 file changed, 11 insertions(+)
>>
>> diff --git a/udp_vu.c b/udp_vu.c
>> index c30dcf97698f..67f4ee619bfb 100644
>> --- a/udp_vu.c
>> +++ b/udp_vu.c
>> @@ -211,6 +211,17 @@ void udp_vu_sock_to_tap(const struct ctx *c, int s, int n, flow_sidx_t tosidx)
>>   	struct vu_virtq *vq = &vdev->vq[VHOST_USER_RX_QUEUE];
>>   	int i;
>>   
>> +	if (!vu_queue_enabled(vq) || !vu_queue_started(vq)) {
>> +		struct msghdr msg = { 0 };
>> +
>> +		debug("Got UDP packet, but RX virtqueue not usable yet");
>> +
>> +		if (recvmsg(s, &msg, MSG_DONTWAIT) < 0)
>> +			debug_perror("Failed to discard datagram");
>> +
>> +		return;
>> +	}
>> +
>>   	for (i = 0; i < n; i++) {
>>   		ssize_t dlen;
>>   		int iov_used;
>> -- 
>> 2.52.0
>>
> 


  reply	other threads:[~2026-01-06  7:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 14:50 Laurent Vivier
2026-01-05 23:28 ` David Gibson
2026-01-06  7:48   ` Laurent Vivier [this message]
2026-01-07  0:17     ` David Gibson

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=92742f50-f095-45af-b43b-4d49254886f6@redhat.com \
    --to=lvivier@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).