From: sashiko-bot@kernel.org
To: "Steffen Trumtrar" <s.trumtrar@pengutronix.de>
Cc: virtualization@lists.linux.dev, bpf@vger.kernel.org,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH net-next v5 7/9] vhost-net: support VIRTIO_NET_F_RX_TSTAMP
Date: Fri, 13 Nov 2026 11:20:31 +0000 [thread overview]
Message-ID: <sashiko-outbox-212707@kernel.org> (raw)
In-Reply-To: <20261112-v6-7-topic-virtio-net-ptp-v5-7-7ab67b572f4f@pengutronix.de>
Thank you for your contribution! Sashiko AI review found no new issues
in this patch, but noticed 1 related pre-existing issue it does not
introduce:
- [Medium] vhost-net: descriptor leak on vnet_hdr copy failure in
handle_rx() [1]
--
commit 454489b63f879c752d31f70af8fbc748e0db8e54
Author: Steffen Trumtrar <s.trumtrar@pengutronix.de>
vhost-net: support VIRTIO_NET_F_RX_TSTAMP
This commit advertises VIRTIO_NET_F_RX_TSTAMP to userspace, sizes the
virtio-net header to include the receive timestamp field when negotiated,
and zeroes the remaining header bytes in handle_rx() when vhost supplies
the header.
> diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
> index 435d8ed3851f3..1b171af105a22 100644
> --- a/drivers/vhost/net.c
> +++ b/drivers/vhost/net.c
[ ... ]
> @@ -1278,6 +1283,16 @@ static void handle_rx(struct vhost_net *net)
> vhost_discard_vq_desc(vq, headcount, ndesc);
> goto out;
> }
> + /* Zero the rest of a header supplied by vhost, e.g. tstamp */
> + if (unlikely(vhost_hlen > hdr_filled)) {
> + size_t rest = vhost_hlen - hdr_filled;
> +
> + if (iov_iter_zero(rest, &fixup) != rest) {
> + vq_err(vq, "Failed vnet_hdr zeroing");
> + vhost_discard_vq_desc(vq, headcount, ndesc);
> + goto out;
> + }
> + }
[Severity: Medium]
This problem wasn't introduced by this patch, but does the error path
just above this hunk leak RX descriptors [1] when copying hdr fails?
drivers/vhost/net.c:handle_rx() {
...
if (unlikely(vhost_hlen)) {
if (copy_to_iter(&hdr, sizeof(hdr),
&fixup) != sizeof(hdr)) {
vq_err(vq, "Unable to write vnet_hdr "
"at addr %p\n", vq->iov->iov_base);
goto out;
}
...
}
Unlike the num_buffers and iov_iter_zero() failure paths, jumping to out
there skips vhost_discard_vq_desc(vq, headcount, ndesc), so the
descriptors consumed by get_rx_bufs() are neither rolled back nor
signalled as used.
[1] https://sashiko.dev/#/bug/linux-a8cbb3ff-e3eb-42fc-9cbf-3422af552e28
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112-v6-7-topic-virtio-net-ptp-v5-0-7ab67b572f4f@pengutronix.de?part=7
next prev parent reply other threads:[~2026-11-13 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 11:19 [PATCH net-next v5 0/9] virtio-net: add receive timestamp support Steffen Trumtrar
2026-11-12 11:19 ` [PATCH net-next v5 1/9] net: ethtool: tsconfig: allow hardware timestamping without a PHC Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 2/9] virtio-net: zero the whole tx header Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 3/9] virtio-net: copy the XDP rx hash before the program runs Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 4/9] virtio-net: move virtio_net_common_hdr to virtio_net.h Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 5/9] virtio-net: support receive timestamp Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 6/9] virtio-net: assert header sizes Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 7/9] vhost-net: support VIRTIO_NET_F_RX_TSTAMP Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot [this message]
2026-11-12 11:19 ` [PATCH net-next v5 8/9] virtio-net: add XDP rx timestamp metadata Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:19 ` [PATCH net-next v5 9/9] tun: add rx timestamp to the vnet header Steffen Trumtrar
2026-11-13 11:20 ` sashiko-bot
2026-11-12 11:26 ` [PATCH net-next v5 0/9] virtio-net: add receive timestamp support netdev-bot+sinfo
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-212707@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eperezma@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=s.trumtrar@pengutronix.de \
--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