From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Gianluca Stivan <me@yawnt.com>,
Chris Kuhn <kuhnchris@kuhnchris.eu>
Subject: Re: [PATCH] tap: With pasta, don't reset on tap errors, handle write failures
Date: Mon, 5 Jun 2023 12:16:34 +1000 [thread overview]
Message-ID: <ZH1FgpluwYS53uZv@yekko> (raw)
In-Reply-To: <20230604054957.619904-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2610 bytes --]
On Sun, Jun 04, 2023 at 07:49:57AM +0200, Stefano Brivio wrote:
> Since commit 0515adceaa8f ("passt, pasta: Namespace-based sandboxing,
> defer seccomp policy application"), it makes no sense to close and
> reopen the tap device on error: we don't have access to /dev/net/tun
> after the initial setup phase.
>
> If we hit ENOBUFS while writing (as reported: in one case because
> the kernel actually ran out of memory, with another case under
> investigation), or ENOSPC, we're supposed to drop whatever data we
> were trying to send: there's no room for it.
>
> Handle EINTR just like we handled EAGAIN/EWOULDBLOCK: there's no
> particular reason why sending the same data should fail again.
>
> Anything else I can think of would be an unrecoverable error: exit
> with failure then.
>
> While at it, drop a useless cast on the write() call: it takes a
> const void * anyway.
>
> Reported-by: Gianluca Stivan <me@yawnt.com>
> Reported-by: Chris Kuhn <kuhnchris@kuhnchris.eu>
> Fixes: 0515adceaa8f ("passt, pasta: Namespace-based sandboxing, defer seccomp policy application")
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> tap.c | 24 +++++++++++++++++++-----
> 1 file changed, 19 insertions(+), 5 deletions(-)
>
> diff --git a/tap.c b/tap.c
> index c0b7f33..e323529 100644
> --- a/tap.c
> +++ b/tap.c
> @@ -320,12 +320,23 @@ static size_t tap_send_frames_pasta(struct ctx *c,
> size_t i;
>
> for (i = 0; i < n; i++) {
> - if (write(c->fd_tap, (char *)iov[i].iov_base,
> - iov[i].iov_len) < 0) {
> + if (write(c->fd_tap, iov[i].iov_base, iov[i].iov_len) < 0) {
> debug("tap write: %s", strerror(errno));
> - if (errno != EAGAIN && errno != EWOULDBLOCK)
> - tap_handler(c, c->fd_tap, EPOLLERR, NULL);
> - i--;
> +
> + switch (errno) {
> + case EAGAIN:
> +#if EAGAIN != EWOULDBLOCK
> + case EWOULDBLOCK:
> +#endif
> + case EINTR:
> + i--;
> + break;
> + case ENOBUFS:
> + case ENOSPC:
> + break;
> + default:
> + die("Write error on tap device, exiting");
> + }
> }
> }
>
> @@ -1237,6 +1248,9 @@ void tap_handler(struct ctx *c, int fd, uint32_t events,
> exit(EXIT_SUCCESS);
> }
>
> + if (c->mode == MODE_PASTA)
> + die("Error on tap device, exiting");
> +
> tap_sock_init(c);
> }
> }
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-06-05 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 5:49 [PATCH] tap: With pasta, don't reset on tap errors, handle write failures Stefano Brivio
2023-06-05 2:16 ` David Gibson [this message]
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=ZH1FgpluwYS53uZv@yekko \
--to=david@gibson.dropbear.id.au \
--cc=kuhnchris@kuhnchris.eu \
--cc=me@yawnt.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).