All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Nirmoy Das <nirmoyd@nvidia.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Sabrina Dubroca <sd@queasysnail.net>,
	John Fastabend <john.fastabend@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: tls: size splice_short pipe by page size
Date: Wed, 24 Jun 2026 13:51:32 +0100	[thread overview]
Message-ID: <20260624125132.GN827683@horms.kernel.org> (raw)
In-Reply-To: <20260622202847.3944076-1-nirmoyd@nvidia.com>

On Mon, Jun 22, 2026 at 01:28:47PM -0700, Nirmoy Das wrote:
> splice_short grows its pipe with (MAX_FRAGS + 1) * 0x1000 so it can
> queue one short vmsplice() buffer for each fragment before draining the
> pipe. That assumes 4K pipe buffers.
> 
> On 64K-page kernels the request is rounded to 262144 bytes, which
> provides only four pipe buffers. The fifth one-byte vmsplice() blocks in
> pipe_wait_writable and the test times out before it reaches the TLS path.
> 
> Request enough bytes for the same number of pipe buffers using the
> runtime page size, and assert that the kernel granted at least that much.
> If an unprivileged run cannot raise the pipe above the system
> pipe-max-size limit, skip the test because it cannot exercise the
> intended path.
> 
> Fixes: 3667e9b442b9 ("selftests: tls: add test for short splice due to full skmsg")
> Assisted-by: Codex:gpt-5
> Signed-off-by: Nirmoy Das <nirmoyd@nvidia.com>

The nit below not withstanding, this looks good to me.

Reviewed-by: Simon Horman <horms@kernel.org>

> ---
>  tools/testing/selftests/net/tls.c | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/net/tls.c b/tools/testing/selftests/net/tls.c
> index 30a236b8e9f73..e3bf4ade0f770 100644
> --- a/tools/testing/selftests/net/tls.c
> +++ b/tools/testing/selftests/net/tls.c
> @@ -997,6 +997,8 @@ TEST_F(tls, splice_short)
>  	char sendbuf[0x100];
>  	char sendchar = 'S';
>  	int pipefds[2];
> +	int pipe_sz;
> +	int ret;
>  	int i;
>  
>  	sendchar_iov.iov_base = &sendchar;
> @@ -1005,7 +1007,12 @@ TEST_F(tls, splice_short)
>  	memset(sendbuf, 's', sizeof(sendbuf));
>  
>  	ASSERT_GE(pipe2(pipefds, O_NONBLOCK), 0);
> -	ASSERT_GE(fcntl(pipefds[0], F_SETPIPE_SZ, (MAX_FRAGS + 1) * 0x1000), 0);
> +	pipe_sz = (MAX_FRAGS + 1) * getpagesize();
> +	ret = fcntl(pipefds[0], F_SETPIPE_SZ, pipe_sz);
> +	if (ret < 0 && errno == EPERM)
> +		SKIP(return, "insufficient pipe capacity");
> +	ASSERT_GE(ret, 0);

nit: the line above seems redundant to me given the line below.

> +	ASSERT_GE(ret, pipe_sz);
>  
>  	for (i = 0; i < MAX_FRAGS; i++)
>  		ASSERT_GE(vmsplice(pipefds[1], &sendchar_iov, 1, 0), 0);
> -- 
> 2.43.0
> 

  reply	other threads:[~2026-06-24 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 20:28 [PATCH net-next] selftests: tls: size splice_short pipe by page size Nirmoy Das
2026-06-24 12:51 ` Simon Horman [this message]
2026-06-24 13:46   ` Nirmoy Das

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=20260624125132.GN827683@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nirmoyd@nvidia.com \
    --cc=sd@queasysnail.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.