public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 1/4] tap: Don't pcap frames that didn't get sent
Date: Wed, 15 Feb 2023 13:17:25 +0100	[thread overview]
Message-ID: <20230215131725.02d3c6fd@elisabeth> (raw)
In-Reply-To: <20230127051110.2513363-2-david@gibson.dropbear.id.au>

On Fri, 27 Jan 2023 16:11:07 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> In tap_send_frames() we send a number of frames to the tap device, then
> also write them to the pcap capture file (if configured).  However the tap
> send can partially fail (short write()s or similar), meaning that some
> of the requested frames weren't actually sent, but we still write those
> frames to the capture file.
> 
> We do give a debug message in this case, but it's misleading to add frames
> that we know weren't sent to the capture file.  Rework to avoid this.

To be really "correct", I guess we should also truncate messages in
captures if they were sent partially, by returning the number of bytes
sent from tap_send_frames_{pasta,passt}() and then modifying the
argument to pcap_frame() in the pcap_multiple() loop.

This is relevant because, if a packet has a checksum, we could consider
it lost while checking captures.

Still, it's a vast improvement on the original, so I would apply this
even like it is -- except for two nits, below:

> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
>  tap.c | 30 ++++++++++++++++++++----------
>  1 file changed, 20 insertions(+), 10 deletions(-)
> 
> diff --git a/tap.c b/tap.c
> index af9bc15..dd22490 100644
> --- a/tap.c
> +++ b/tap.c
> @@ -309,10 +309,12 @@ void tap_icmp6_send(const struct ctx *c,
>   * @iov:	Array of buffers, each containing one frame
>   * @n:		Number of buffers/frames in @iov
>   *
> + * Returns: number of frames successfully sent

For consistency: "Return:" -- I see now that one slipped through in
pcap_frame(). I can "fix" this on merge or in a follow-up patch, too.

> + *
>   * #syscalls:pasta write
>   */
> -static void tap_send_frames_pasta(struct ctx *c,
> -				  const struct iovec *iov, size_t n)
> +static size_t tap_send_frames_pasta(struct ctx *c,
> +				    const struct iovec *iov, size_t n)
>  {
>  	size_t i;
>  
> @@ -324,6 +326,8 @@ static void tap_send_frames_pasta(struct ctx *c,
>  			i--;
>  		}
>  	}
> +
> +	return n;
>  }
>  
>  /**
> @@ -356,10 +360,12 @@ static void tap_send_remainder(const struct ctx *c, const struct iovec *iov,
>   * @iov:	Array of buffers, each containing one frame
>   * @n:		Number of buffers/frames in @iov
>   *
> + * Returns: number of frames successfully sent

Same here.

-- 
Stefano


  reply	other threads:[~2023-02-15 12:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27  5:11 [PATCH 0/4] RFC: Some cleanups to tap and tcp David Gibson
2023-01-27  5:11 ` [PATCH 1/4] tap: Don't pcap frames that didn't get sent David Gibson
2023-02-15 12:17   ` Stefano Brivio [this message]
2023-02-16  5:20     ` David Gibson
2023-02-16  7:43       ` Stefano Brivio
2023-01-27  5:11 ` [PATCH 2/4] tap: Eliminate goto from tap_handler() David Gibson
2023-01-27  5:11 ` [PATCH 3/4] tcp: Remove 'recvmsg' goto from tcp_data_from_sock David Gibson
2023-02-15 12:17   ` Stefano Brivio
2023-02-16  0:28     ` David Gibson
2023-01-27  5:11 ` [PATCH 4/4] tcp: Remove 'zero_len' " David Gibson

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=20230215131725.02d3c6fd@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    /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).