From: Chuck Lever <cel@kernel.org>
To: John Fastabend <john.fastabend@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Sabrina Dubroca <sd@queasysnail.net>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Chuck Lever <cel@kernel.org>, Dave Watson <davejwatson@fb.com>,
Shuah Khan <shuah@kernel.org>,
Qingfang Deng <qingfang.deng@linux.dev>,
Eric Dumazet <edumazet@kernel.org>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH net-next v2 8/8] selftests: tls: cover splice on a nonblocking socket
Date: Thu, 01 Oct 2026 18:41:40 -0400 [thread overview]
Message-ID: <20261001-tls-follow-on-v2-8-2dd1947bb642@kernel.org> (raw)
In-Reply-To: <20261001-tls-follow-on-v2-0-2dd1947bb642@kernel.org>
Every existing splice call in this file either passes
SPLICE_F_NONBLOCK or runs on a blocking socket, so nothing
exercises the socket's own O_NONBLOCK on the splice path. A change
that stops consulting sock->file->f_flags puts splice(2) and
sendfile(2) back to sleeping in tls_rx_rec_wait() while a peer
streams empty records, and the suite still reports pass.
Run the zero-length record variants a second time with O_NONBLOCK
set on the socket and SPLICE_F_NONBLOCK left out of the splice
flags. Both forms must reach the same outcome, so the existing
per-variant expectations carry over. A kernel that ignores the
socket flag sleeps in the EAGAIN variant until the harness
timeout rather than returning.
Signed-off-by: Chuck Lever <cel@kernel.org>
---
tools/testing/selftests/net/tls.c | 40 +++++++++++++++++++++++++++++++++------
1 file changed, 34 insertions(+), 6 deletions(-)
diff --git a/tools/testing/selftests/net/tls.c b/tools/testing/selftests/net/tls.c
index e6876b8caac8..6207a90c5f07 100644
--- a/tools/testing/selftests/net/tls.c
+++ b/tools/testing/selftests/net/tls.c
@@ -2820,23 +2820,24 @@ FIXTURE_TEARDOWN(zero_len_splice)
* A control record behind the run reports EINVAL, the error splice
* already reports for a control record it meets first.
*/
-TEST_F(zero_len_splice, test)
+static void
+zero_len_do_splice(struct __test_metadata *_metadata,
+ FIXTURE_DATA(zero_len_splice) *self,
+ const FIXTURE_VARIANT(zero_len_splice) *variant,
+ unsigned int splice_flags)
{
const struct raw_rec *payload;
unsigned char buf[128];
ssize_t ret;
int p[2];
- if (self->notls)
- SKIP(return, "no TLS support");
-
ASSERT_GE(pipe(p), 0);
payload = zero_len_send_recs(_metadata, self->fd, variant->recs);
if (variant->splice_ret < 0) {
ret = splice(self->cfd, NULL, p[1], NULL, sizeof(buf),
- SPLICE_F_NONBLOCK);
+ splice_flags);
EXPECT_EQ(ret, -1);
EXPECT_EQ(errno, -variant->splice_ret);
} else {
@@ -2844,7 +2845,7 @@ TEST_F(zero_len_splice, test)
* below would block until the harness timeout.
*/
ASSERT_EQ(splice(self->cfd, NULL, p[1], NULL, sizeof(buf),
- SPLICE_F_NONBLOCK), variant->splice_ret);
+ splice_flags), variant->splice_ret);
ret = read(p[0], buf, sizeof(buf));
EXPECT_EQ(ret, variant->splice_ret);
if (ret == variant->splice_ret)
@@ -2861,6 +2862,33 @@ TEST_F(zero_len_splice, test)
close(p[1]);
}
+TEST_F(zero_len_splice, test)
+{
+ if (self->notls)
+ SKIP(return, "no TLS support");
+
+ zero_len_do_splice(_metadata, self, variant, SPLICE_F_NONBLOCK);
+}
+
+/* The socket's O_NONBLOCK governs the record wait, as on a plain TCP
+ * socket, so a splice without SPLICE_F_NONBLOCK behaves like one that
+ * sets it. Deriving the wait from SPLICE_F_NONBLOCK alone sleeps here
+ * until the harness timeout.
+ */
+TEST_F(zero_len_splice, nonblock_socket)
+{
+ int sflags;
+
+ if (self->notls)
+ SKIP(return, "no TLS support");
+
+ sflags = fcntl(self->cfd, F_GETFL, 0);
+ ASSERT_GE(sflags, 0);
+ ASSERT_EQ(fcntl(self->cfd, F_SETFL, sflags | O_NONBLOCK), 0);
+
+ zero_len_do_splice(_metadata, self, variant, 0);
+}
+
FIXTURE(tls_err)
{
int fd, cfd;
--
2.55.0
next prev parent reply other threads:[~2026-10-01 22:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 22:41 [PATCH net-next v2 0/8] net/tls: Receive-path fixes for zero-length data records Chuck Lever
2026-10-01 22:41 ` [PATCH net-next v2 1/8] tls: bound consecutive no-data records in tls_sw_read_sock() Chuck Lever
2026-10-05 23:22 ` netdev-bot+sashiko
2026-10-06 15:44 ` Chuck Lever
2026-10-01 22:41 ` [PATCH net-next v2 2/8] tls: check for a pending signal after an empty record Chuck Lever
2026-10-05 23:22 ` netdev-bot+sashiko
2026-10-06 15:45 ` Chuck Lever
2026-10-01 22:41 ` [PATCH net-next v2 3/8] tls: consume empty data records in tls_sw_splice_read() Chuck Lever
2026-10-05 23:22 ` netdev-bot+sashiko
2026-10-06 15:45 ` Chuck Lever
2026-10-01 22:41 ` [PATCH net-next v2 4/8] tls: honor O_NONBLOCK " Chuck Lever
2026-10-05 23:22 ` netdev-bot+sashiko
2026-10-06 15:46 ` Chuck Lever
2026-10-01 22:41 ` [PATCH net-next v2 5/8] tls: consume empty data records in tls_sw_recvmsg() Chuck Lever
2026-10-05 23:22 ` netdev-bot+sashiko
2026-10-06 15:47 ` Chuck Lever
2026-10-01 22:41 ` [PATCH net-next v2 6/8] selftests: tls: add peek and splice coverage for zero-length records Chuck Lever
2026-10-05 23:22 ` netdev-bot+sashiko
2026-10-01 22:41 ` [PATCH net-next v2 7/8] selftests: tls: skip the zero_len tests when TLS is unavailable Chuck Lever
2026-10-05 23:22 ` netdev-bot+sashiko
2026-10-01 22:41 ` Chuck Lever [this message]
2026-10-01 22:45 ` [PATCH net-next v2 0/8] net/tls: Receive-path fixes for zero-length data records netdev-bot+sinfo
2026-10-02 15:30 ` Chuck Lever
2026-10-04 6:36 ` Qingfang Deng
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=20261001-tls-follow-on-v2-8-2dd1947bb642@kernel.org \
--to=cel@kernel.org \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@linux.dev \
--cc=sd@queasysnail.net \
--cc=shuah@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox