Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: chanyoung <ppoo1220@gmail.com>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, John Fastabend <john.fastabend@gmail.com>,
	Jakub Kicinski <kuba@kernel.org>,
	David Howells <dhowells@redhat.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org, chanyoung <ppoo1220@gmail.com>
Subject: Re: [PATCH net 2/2] selftests: tls: add a test for splicing onto a full plaintext record
Date: Mon, 27 Jul 2026 21:59:47 +0900	[thread overview]
Message-ID: <20260727125947.2889407-1-ppoo1220@gmail.com> (raw)
In-Reply-To: <amdHFJlOVpACBir6@krikkit>

2026-07-27, 13:55:00 +0200, Sabrina Dubroca wrote:
> Why 4 extra splices? One should be enough to hit tls_sw_sendmsg_splice
> with the skmsg already full?

You're right, one is enough - I checked, same oops.

> Do we really need a fresh pipe for each iteration?

No, one reused pipe works.

All four fixed in v2. The reworked test still reproduces on an unpatched
kernel.

Thanks,
chanyoung

      reply	other threads:[~2026-07-27 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26 10:55 [PATCH net 0/2] tls: fix plaintext sk_msg ring over-fill in tls_sw_sendmsg_splice() chanyoung
2026-07-26 10:55 ` [PATCH net 1/2] tls: don't over-fill the plaintext sk_msg ring " chanyoung
2026-07-27 10:30   ` Sabrina Dubroca
2026-07-27 12:58     ` chanyoung
2026-07-26 10:55 ` [PATCH net 2/2] selftests: tls: add a test for splicing onto a full plaintext record chanyoung
2026-07-27 11:55   ` Sabrina Dubroca
2026-07-27 12:59     ` chanyoung [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=20260727125947.2889407-1-ppoo1220@gmail.com \
    --to=ppoo1220@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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