From: David Gibson <david@gibson.dropbear.id.au>
To: Yumei Huang <yuhuang@redhat.com>
Cc: passt-dev@passt.top, sbrivio@redhat.com, lvivier@redhat.com
Subject: Re: [PATCH v2] tap: Drop frames if no client connected
Date: Mon, 15 Sep 2025 11:59:29 +1000 [thread overview]
Message-ID: <aMdzAfzGTZWZeVbM@zatzit> (raw)
In-Reply-To: <20250912081705.20796-1-yuhuang@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2990 bytes --]
On Fri, Sep 12, 2025 at 04:17:05PM +0800, Yumei Huang wrote:
> If no client is attached, discard outgoing frames and report them as
> sent. Without this we will get an EBADF in either writev() (pasta) or
> sendmsg() (passt). That's basically harmless, but a bit ugly.
> Explicitly catching this case results in behaviour that's probably a
> bit clearer to debug if we hit it.
>
> There are several different approaches we can take here. Here's some
> reasoning as David explained:
>
> * Don't listen() until the tap connection is ready
>
> - It's not clear that the host rejecting the connection is better
> than the host accepting, then the connection stalling until the
> guest is ready.
> - Would require substantial rework because we currently listen() as
> we parse the command line and don't store the information we'd need
> to do it later.
>
> * Don't accept() until the tap connection is ready
>
> - To the peer, will behave basically the same as this patch - the
> host will complete the TCP handshake, then the connection will stall
> until the guest is ready.
> - More work to implement, because essentially every sock-side handler
> has to check fd_tap and abort early
>
> * Drop packets in tap_send_frames(), but return 0
>
> - To the peer, would behave basically the same
> - Would make the TCP code do a bunch of busy work attempting to
> resend, probably to no avail
> - Handling of errors returned by tap_send_frames() is on the basis
> that it's probably a transient fault (buffer full) and we want to
> resend very soon. That approach doesn't make sense for a missing
> guest.
>
> Suggested-by: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Yumei Huang <yuhuang@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> tap.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/tap.c b/tap.c
> index 7ba6399..2e371b3 100644
> --- a/tap.c
> +++ b/tap.c
> @@ -507,13 +507,16 @@ static size_t tap_send_frames_passt(const struct ctx *c,
> * @iov must have total length @bufs_per_frame * @nframes, with each set of
> * @bufs_per_frame contiguous buffers representing a single frame.
> *
> - * Return: number of frames actually sent
> + * Return: number of frames actually sent, or accounted as sent
I don't think it's worth a respin, but this might be better phrased as:
"number of frames actually sent, or silently dropped"
> */
> size_t tap_send_frames(const struct ctx *c, const struct iovec *iov,
> size_t bufs_per_frame, size_t nframes)
> {
> size_t m;
>
> + if (c->fd_tap == -1)
> + return nframes;
> +
> if (!nframes)
> return 0;
>
> --
> 2.47.0
>
--
David Gibson (he or they) | 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:[~2025-09-15 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 8:17 [PATCH v2] tap: Drop frames if no client connected Yumei Huang
2025-09-15 1:59 ` 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=aMdzAfzGTZWZeVbM@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
--cc=yuhuang@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).