From: sashiko-bot@kernel.org
To: raoxu <raoxu@uniontech.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH] vhost/net: Fix receive queue test in busy poll
Date: Wed, 11 Nov 2026 05:19:32 +0000 [thread overview]
Message-ID: <sashiko-outbox-208329@kernel.org> (raw)
In-Reply-To: <005FA5F7354482C7+20261110051642.249640-1-raoxu@uniontech.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] vhost/net: missing Fixes trailer for sock_has_rx_data() bug fix
--
commit e704f9e65e5ab760d5f0c63a3cc9fef9370b05b7
Author: Xu Rao <raoxu@uniontech.com>
> vhost/net: Fix receive queue test in busy poll
>
> sock_has_rx_data() returns a positive result when receive data is
> available. Socket implementations with a peek_len() callback follow
> that convention, but the fallback for sockets without one returns
> skb_queue_empty(), which has the opposite meaning.
>
> This makes busy polling stop when a raw packet socket has no queued data
> and fail to recognize queued data through the fallback path. Return the
> negated queue-empty result so the fallback matches the callback and its
> callers.
>
> Signed-off-by: Xu Rao <raoxu@uniontech.com>
[Severity: Low]
The inverted skb_queue_empty() return value was introduced by
1576d9860599 ("tun: switch to use skb array for tx") and later moved to
sock_has_rx_data() by dc151282bbda ("net: vhost: factor out busy polling
logic to vhost_net_busy_poll()"). Should this include a Fixes tag, such
as:
Fixes: 1576d9860599 ("tun: switch to use skb array for tx")
--
Sashiko AI review · https://sashiko.dev/#/patchset/005FA5F7354482C7+20261110051642.249640-1-raoxu@uniontech.com?part=1
next prev parent reply other threads:[~2026-11-11 5:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 5:16 [PATCH] vhost/net: Fix receive queue test in busy poll raoxu
2026-11-11 5:19 ` sashiko-bot [this message]
2026-11-11 11:58 ` Björn Töpel
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-208329@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=raoxu@uniontech.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