From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Leo Stone <leocstone@gmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org
Cc: Leo Stone <leocstone@gmail.com>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH net-next] selftests: net/psock_lib: Handle EINTR and EAGAIN
Date: Mon, 18 Nov 2024 10:02:15 -0500 [thread overview]
Message-ID: <673b56f7768fc_1ced1f294fa@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20241117225950.138968-1-leocstone@gmail.com>
Leo Stone wrote:
> Make pair_udp_send_char handle EAGAIN, EINTR, and partial reads or
> writes.
>
> Signed-off-by: Leo Stone <leocstone@gmail.com>
Did you observe actual issues or is this based on the comment in the
existing code ("Should really handle EINTR and EAGAIN").
AFAIK all the users of psock_lib use default blocking IO, so should
not see EAGAIN.
A simpler approach to dealing with EINTR is to ask glibc to restart
with sigaction or siginterrupt.
> ---
> tools/testing/selftests/net/psock_lib.h | 39 +++++++++++++++++++------
> 1 file changed, 30 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/selftests/net/psock_lib.h b/tools/testing/selftests/net/psock_lib.h
> index 6e4fef560873..e28bff95c8e2 100644
> --- a/tools/testing/selftests/net/psock_lib.h
> +++ b/tools/testing/selftests/net/psock_lib.h
> @@ -13,6 +13,7 @@
> #include <string.h>
> #include <arpa/inet.h>
> #include <unistd.h>
> +#include <stdbool.h>
>
> #include "kselftest.h"
>
> @@ -110,21 +111,41 @@ static __maybe_unused void pair_udp_open(int fds[], uint16_t port)
> }
> }
>
> +static void read_write_checked(int fd, char *buf, size_t sz, bool is_write)
> +{
> + int bytes_processed = 0;
> + int ret;
> +
> + do {
> + if (is_write)
> + ret = write(fd, buf + bytes_processed,
> + sz - bytes_processed);
> + else
> + ret = read(fd, buf + bytes_processed,
> + sz - bytes_processed);
> + if (ret == -1) {
> + if (errno == EAGAIN || errno == EINTR) {
> + continue;
Instead of busy looping, on return with EAGAIN should probably block.
> + } else {
> + fprintf(stderr, "ERROR: %s failed, bytes left=%lu\n",
> + is_write ? "send" : "recv",
> + sz - bytes_processed);
> + exit(1);
> + }
> + }
> + bytes_processed += ret;
> + } while (bytes_processed < sz);
> +}
> +
> static __maybe_unused void pair_udp_send_char(int fds[], int num, char payload)
> {
> char buf[DATA_LEN], rbuf[DATA_LEN];
>
> memset(buf, payload, sizeof(buf));
> while (num--) {
> - /* Should really handle EINTR and EAGAIN */
> - if (write(fds[0], buf, sizeof(buf)) != sizeof(buf)) {
> - fprintf(stderr, "ERROR: send failed left=%d\n", num);
> - exit(1);
> - }
> - if (read(fds[1], rbuf, sizeof(rbuf)) != sizeof(rbuf)) {
> - fprintf(stderr, "ERROR: recv failed left=%d\n", num);
> - exit(1);
> - }
> + read_write_checked(fds[0], buf, sizeof(buf), true);
> + read_write_checked(fds[1], rbuf, sizeof(rbuf), false);
> +
> if (memcmp(buf, rbuf, sizeof(buf))) {
> fprintf(stderr, "ERROR: data failed left=%d\n", num);
> exit(1);
> --
> 2.39.5
>
next prev parent reply other threads:[~2024-11-18 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 22:59 Leo Stone
2024-11-18 15:02 ` Willem de Bruijn [this message]
2024-11-21 1:25 ` Leo Stone
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=673b56f7768fc_1ced1f294fa@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leocstone@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®