public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Jon Maloy <jmaloy@redhat.com>
To: passt-dev@passt.top, sbrivio@redhat.com, lvivier@redhat.com,
	dgibson@redhat.com
Subject: Re: [PATCH] tcp: probe for SO_PEEK_OFF both in tcpv4 and tcp6
Date: Sat, 20 Jul 2024 10:46:07 -0400	[thread overview]
Message-ID: <a2d633f4-3be6-451b-a3c5-1b6cc0e6032a@redhat.com> (raw)
In-Reply-To: <20240720135453.2694694-1-jmaloy@redhat.com>

My first approach to this was to condition the use of SO_PEEK_OFF with 
tcpv4, e.g., basically
a test like if (v4 && peek_offset_cap) {...} everywhere, but then I made 
an interesting discovery.

It turns out that, unless the ´-4' option is explicitly given on the 
command line, all sockets are
v6, even those that are later used as v4 sockets. So, the set_peek_off() 
call failed even
for supposedly v4 sockets.

I checked this by adding a printout to the tcp_listen_handler(), and 
noticed that all returns from
the accept4() call goes into the AF_INET6 branch, even when the client 
(iperf3) call is using an IPv4 address.
During traffic, the very same socket is marked as v4 in the tcp_tap_conn 
structure, and this seems to
have worked just fine until I added the set_peek_offset call().

I believe this is an issue that has been introduced during the last 
months, since I didn't start
using the ´-4' option consistently until some months ago, and then it 
worked.

Happy summer
///jon


On 2024-07-20 09:54, Jon Maloy wrote:
> The recently added socket option SO_PEEK_OFF is not supported for
> TCP/IPv6 sockets. Until we get that support into the kernel we need to
> test for support in both protocols to set the global 'peek_offset_cap´
> to true.
>
> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
> ---
>   tcp.c | 36 +++++++++++++++++++++++++-----------
>   1 file changed, 25 insertions(+), 11 deletions(-)
>
> diff --git a/tcp.c b/tcp.c
> index c5431f1..32026ca 100644
> --- a/tcp.c
> +++ b/tcp.c
> @@ -2717,6 +2717,28 @@ static void tcp_sock_refill_init(const struct ctx *c)
>   	}
>   }
>   
> +/**
> + * tcp_probe_peek_offset_cap() - Check if SO_PEEK_OFF is supported by kernel
> + * @af:		Address family, IPv4 or IPv6
> + *
> + * Return: true if supported, false otherwise
> + */
> +bool tcp_probe_peek_offset_cap(int af)
> +{
> +	bool ret = false;
> +	int s, optv = 0;
> +
> +	s = socket(af, SOCK_STREAM | SOCK_CLOEXEC, IPPROTO_TCP);
> +	if (s < 0) {
> +		warn_perror("Temporary TCP socket creation failed");
> +	} else {
> +		if (!setsockopt(s, SOL_SOCKET, SO_PEEK_OFF, &optv, sizeof(int)))
> +			ret = true;
> +		close(s);
> +	}
> +	return ret;
> +}
> +
>   /**
>    * tcp_init() - Get initial sequence, hash secret, initialise per-socket data
>    * @c:		Execution context
> @@ -2725,8 +2747,7 @@ static void tcp_sock_refill_init(const struct ctx *c)
>    */
>   int tcp_init(struct ctx *c)
>   {
> -	unsigned int b, optv = 0;
> -	int s;
> +	unsigned int b;
>   
>   	ASSERT(!c->no_tcp);
>   
> @@ -2752,15 +2773,8 @@ int tcp_init(struct ctx *c)
>   		NS_CALL(tcp_ns_socks_init, c);
>   	}
>   
> -	/* Probe for SO_PEEK_OFF support */
> -	s = socket(AF_INET, SOCK_STREAM | SOCK_CLOEXEC, IPPROTO_TCP);
> -	if (s < 0) {
> -		warn_perror("Temporary TCP socket creation failed");
> -	} else {
> -		if (!setsockopt(s, SOL_SOCKET, SO_PEEK_OFF, &optv, sizeof(int)))
> -			peek_offset_cap = true;
> -		close(s);
> -	}
> +	peek_offset_cap = tcp_probe_peek_offset_cap(AF_INET) &&
> +		tcp_probe_peek_offset_cap(AF_INET6);
>   	info("SO_PEEK_OFF%ssupported", peek_offset_cap ? " " : " not ");
>   
>   	return 0;


  reply	other threads:[~2024-07-20 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20 13:54 [PATCH] tcp: probe for SO_PEEK_OFF both in tcpv4 and tcp6 Jon Maloy
2024-07-20 14:46 ` Jon Maloy [this message]
2024-07-21  9:21   ` Stefano Brivio
2024-07-22  0:55     ` David Gibson
2024-07-21  9:20 ` Stefano Brivio

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=a2d633f4-3be6-451b-a3c5-1b6cc0e6032a@redhat.com \
    --to=jmaloy@redhat.com \
    --cc=dgibson@redhat.com \
    --cc=lvivier@redhat.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).