From: Stefano Garzarella <sgarzare@redhat.com>
To: Michal Luczaj <mhal@rbox.co>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Arseniy Krasnov" <avkrasnov@salutedevices.com>,
kvm@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] vsock/test: Add test for a linear and non-linear skb getting coalesced
Date: Fri, 9 Jan 2026 17:32:22 +0100 [thread overview]
Message-ID: <aWEqjjE1vb_t35lQ@sgarzare-redhat> (raw)
In-Reply-To: <20260108-vsock-recv-coalescence-v1-2-26f97bb9a99b@rbox.co>
On Thu, Jan 08, 2026 at 10:54:55AM +0100, Michal Luczaj wrote:
>Loopback transport can mangle data in rx queue when a linear skb is
>followed by a small MSG_ZEROCOPY packet.
Can we describe a bit more what the test is doing?
>
>Signed-off-by: Michal Luczaj <mhal@rbox.co>
>---
> tools/testing/vsock/vsock_test.c | 5 +++
> tools/testing/vsock/vsock_test_zerocopy.c | 67 +++++++++++++++++++++++++++++++
> tools/testing/vsock/vsock_test_zerocopy.h | 3 ++
> 3 files changed, 75 insertions(+)
>
>diff --git a/tools/testing/vsock/vsock_test.c b/tools/testing/vsock/vsock_test.c
>index bbe3723babdc..21c8616100f1 100644
>--- a/tools/testing/vsock/vsock_test.c
>+++ b/tools/testing/vsock/vsock_test.c
>@@ -2403,6 +2403,11 @@ static struct test_case test_cases[] = {
> .run_client = test_stream_accepted_setsockopt_client,
> .run_server = test_stream_accepted_setsockopt_server,
> },
>+ {
>+ .name = "SOCK_STREAM MSG_ZEROCOPY coalescence corruption",
This is essentially a regression test for virtio transport, so I'd add
virtio in the test name.
>+ .run_client = test_stream_msgzcopy_mangle_client,
>+ .run_server = test_stream_msgzcopy_mangle_server,
>+ },
> {},
> };
>
>diff --git a/tools/testing/vsock/vsock_test_zerocopy.c b/tools/testing/vsock/vsock_test_zerocopy.c
>index 9d9a6cb9614a..6735a9d7525d 100644
>--- a/tools/testing/vsock/vsock_test_zerocopy.c
>+++ b/tools/testing/vsock/vsock_test_zerocopy.c
>@@ -9,11 +9,13 @@
> #include <stdio.h>
> #include <stdlib.h>
> #include <string.h>
>+#include <sys/ioctl.h>
> #include <sys/mman.h>
> #include <unistd.h>
> #include <poll.h>
> #include <linux/errqueue.h>
> #include <linux/kernel.h>
>+#include <linux/sockios.h>
> #include <errno.h>
>
> #include "control.h"
>@@ -356,3 +358,68 @@ void test_stream_msgzcopy_empty_errq_server(const struct test_opts *opts)
> control_expectln("DONE");
> close(fd);
> }
>+
>+#define GOOD_COPY_LEN 128 /* net/vmw_vsock/virtio_transport_common.c */
I think we don't need this, I mean we can eventually just send a single
byte, no?
>+
>+void test_stream_msgzcopy_mangle_client(const struct test_opts *opts)
>+{
>+ char sbuf1[PAGE_SIZE + 1], sbuf2[GOOD_COPY_LEN];
>+ struct pollfd fds;
>+ int fd;
>+
>+ fd = vsock_stream_connect(opts->peer_cid, opts->peer_port);
>+ if (fd < 0) {
>+ perror("connect");
>+ exit(EXIT_FAILURE);
>+ }
>+
>+ enable_so_zerocopy_check(fd);
>+
>+ memset(sbuf1, '1', sizeof(sbuf1));
>+ memset(sbuf2, '2', sizeof(sbuf2));
>+
>+ send_buf(fd, sbuf1, sizeof(sbuf1), 0, sizeof(sbuf1));
>+ send_buf(fd, sbuf2, sizeof(sbuf2), MSG_ZEROCOPY, sizeof(sbuf2));
>+
>+ fds.fd = fd;
>+ fds.events = 0;
>+
>+ if (poll(&fds, 1, -1) != 1 || !(fds.revents & POLLERR)) {
>+ perror("poll");
>+ exit(EXIT_FAILURE);
>+ }
Should we also call vsock_recv_completion() or we don't care about the
result?
If we need it, maybe we can factor our the poll +
vsock_recv_completion().
>+
>+ close(fd);
>+}
>+
>+static void recv_verify(int fd, char *buf, unsigned int len, char pattern)
>+{
>+ recv_buf(fd, buf, len, 0, len);
>+
>+ while (len--) {
>+ if (*buf++ != pattern) {
>+ fprintf(stderr, "Incorrect data received\n");
>+ exit(EXIT_FAILURE);
>+ }
>+ }
>+}
>+
>+void test_stream_msgzcopy_mangle_server(const struct test_opts *opts)
>+{
>+ char rbuf[PAGE_SIZE + 1];
>+ int fd;
>+
>+ fd = vsock_stream_accept(VMADDR_CID_ANY, opts->peer_port, NULL);
>+ if (fd < 0) {
>+ perror("accept");
>+ exit(EXIT_FAILURE);
>+ }
>+
>+ /* Wait, don't race the (buggy) skbs coalescence. */
>+ vsock_ioctl_int(fd, SIOCINQ, PAGE_SIZE + 1 + GOOD_COPY_LEN);
This is cool, another option is to add a barrier here (and after the
poll), but yeah, this should be even better.
Thanks,
Stefano
>+
>+ recv_verify(fd, rbuf, PAGE_SIZE + 1, '1');
>+ recv_verify(fd, rbuf, GOOD_COPY_LEN, '2');
>+
>+ close(fd);
>+}
>diff --git a/tools/testing/vsock/vsock_test_zerocopy.h b/tools/testing/vsock/vsock_test_zerocopy.h
>index 3ef2579e024d..d46c91a69f16 100644
>--- a/tools/testing/vsock/vsock_test_zerocopy.h
>+++ b/tools/testing/vsock/vsock_test_zerocopy.h
>@@ -12,4 +12,7 @@ void test_seqpacket_msgzcopy_server(const struct test_opts *opts);
> void test_stream_msgzcopy_empty_errq_client(const struct test_opts *opts);
> void test_stream_msgzcopy_empty_errq_server(const struct test_opts
> *opts);
>
>+void test_stream_msgzcopy_mangle_client(const struct test_opts *opts);
>+void test_stream_msgzcopy_mangle_server(const struct test_opts *opts);
>+
> #endif /* VSOCK_TEST_ZEROCOPY_H */
>
>--
>2.52.0
>
next prev parent reply other threads:[~2026-01-09 16:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 9:54 [PATCH 0/2] vsock/virtio: Fix data loss/disclosure due to joining of non-linear skb in RX queue Michal Luczaj
2026-01-08 9:54 ` [PATCH 1/2] vsock/virtio: Coalesce only linear skb Michal Luczaj
2026-01-09 16:18 ` Stefano Garzarella
2026-01-11 10:59 ` Michal Luczaj
2026-01-12 14:07 ` Stefano Garzarella
2026-01-08 9:54 ` [PATCH 2/2] vsock/test: Add test for a linear and non-linear skb getting coalesced Michal Luczaj
2026-01-09 16:32 ` Stefano Garzarella [this message]
2026-01-11 10:59 ` Michal Luczaj
2026-01-12 13:44 ` Stefano Garzarella
2026-01-12 15:52 ` Michal Luczaj
2026-01-12 16:48 ` Stefano Garzarella
2026-01-12 21:20 ` Michal Luczaj
2026-01-13 9:36 ` Stefano Garzarella
2026-01-13 15:11 ` Michal Luczaj
2026-01-08 9:58 ` [PATCH 0/2] vsock/virtio: Fix data loss/disclosure due to joining of non-linear skb in RX queue Michal Luczaj
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=aWEqjjE1vb_t35lQ@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=avkrasnov@salutedevices.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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