From: Luigi Leonardi <leonardi@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Arseniy Krasnov <avkrasnov@salutedevices.com>,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev
Subject: Re: [PATCH net] vsock/test: fix send_buf()/recv_buf() EINTR handling
Date: Fri, 3 Apr 2026 14:10:13 +0200 [thread overview]
Message-ID: <ac-uFMz-tFFQIOAE@leonardi-redhat> (raw)
In-Reply-To: <20260403093251.30662-1-sgarzare@redhat.com>
On Fri, Apr 03, 2026 at 11:32:51AM +0200, Stefano Garzarella wrote:
>From: Stefano Garzarella <sgarzare@redhat.com>
>
>When send() or recv() returns -1 with errno == EINTR, the code skips
>the break but still adds the return value to nwritten/nread, making it
>decrease by 1. This leads to wrong buffer offsets and wrong bytes count.
>
>Fix it by explicitly continuing the loop on EINTR, so the return value
>is only added when it is positive.
>
>Fixes: a8ed71a27ef5 ("vsock/test: add recv_buf() utility function")
>Fixes: 12329bd51fdc ("vsock/test: add send_buf() utility function")
>Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
>---
> tools/testing/vsock/util.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
>diff --git a/tools/testing/vsock/util.c b/tools/testing/vsock/util.c
>index 9430ef5b8bc3..1fe1338c79cd 100644
>--- a/tools/testing/vsock/util.c
>+++ b/tools/testing/vsock/util.c
>@@ -344,7 +344,9 @@ void send_buf(int fd, const void *buf, size_t len, int flags,
> ret = send(fd, buf + nwritten, len - nwritten, flags);
> timeout_check("send");
>
>- if (ret == 0 || (ret < 0 && errno != EINTR))
>+ if (ret < 0 && errno == EINTR)
>+ continue;
>+ if (ret <= 0)
> break;
>
> nwritten += ret;
>@@ -396,7 +398,9 @@ void recv_buf(int fd, void *buf, size_t len, int flags, ssize_t expected_ret)
> ret = recv(fd, buf + nread, len - nread, flags);
> timeout_check("recv");
>
>- if (ret == 0 || (ret < 0 && errno != EINTR))
>+ if (ret < 0 && errno == EINTR)
>+ continue;
>+ if (ret <= 0)
> break;
>
> nread += ret;
>--
>2.53.0
>
LGTM!
Reviewed-by: Luigi Leonardi <leonardi@redhat.com>
next prev parent reply other threads:[~2026-04-03 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 9:32 [PATCH net] vsock/test: fix send_buf()/recv_buf() EINTR handling Stefano Garzarella
2026-04-03 12:10 ` Luigi Leonardi [this message]
2026-04-07 1:50 ` patchwork-bot+netdevbpf
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=ac-uFMz-tFFQIOAE@leonardi-redhat \
--to=leonardi@redhat.com \
--cc=avkrasnov@salutedevices.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.