From: Wilfred Mallawa <wilfred.mallawa@wdc.com>
To: "horms@kernel.org" <horms@kernel.org>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"sd@queasysnail.net" <sd@queasysnail.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v7 1/2] net/tls: support setting the maximum payload size
Date: Tue, 21 Oct 2025 23:23:11 +0000 [thread overview]
Message-ID: <018f3da122b80b7f1ba28bfd4b813eb8879fce19.camel@wdc.com> (raw)
In-Reply-To: <aPdwGJGUxhqiocBX@horms.kernel.org>
On Tue, 2025-10-21 at 12:35 +0100, Simon Horman wrote:
> On Tue, Oct 21, 2025 at 07:29:17PM +1000, Wilfred Mallawa wrote:
>
> ...
>
> > diff --git a/Documentation/networking/tls.rst
> > b/Documentation/networking/tls.rst
> > index 36cc7afc2527..ecaa7631ec46 100644
> > --- a/Documentation/networking/tls.rst
> > +++ b/Documentation/networking/tls.rst
> > @@ -280,6 +280,28 @@ If the record decrypted turns out to had been
> > padded or is not a data
> > record it will be decrypted again into a kernel buffer without
> > zero copy.
> > Such events are counted in the ``TlsDecryptRetry`` statistic.
> >
> > +TLS_TX_MAX_PAYLOAD_LEN
> > +~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +Specifies the maximum size of the plaintext payload for
> > transmitted TLS records.
> > +
> > +When this option is set, the kernel enforces the specified limit
> > on all outgoing
> > +TLS records. No plaintext fragment will exceed this size. This
> > option can be used
> > +to implement the TLS Record Size Limit extension [1].
> > + - For TLS 1.2, the value corresponds directly to the
> > record size limit.
>
> Hi Wilfred,
>
> Unfortunately make htmldocs seems unhappy with the line above.
>
> .../tls.rst:291: ERROR: Unexpected indentation. [docutils]
>
> This was with Sphinx 8.1.3.
Hey Simon,
Ah I didn't realise this wasn't allowed, will fixup and test with make
htmldocs.
Thanks!
Wilfred
>
> > + - For TLS 1.3, the value should be set to
> > record_size_limit - 1, since
> > + the record size limit includes one additional byte for
> > the ContentType
> > + field.
> > +
> > +The valid range for this option is 64 to 16384 bytes for TLS 1.2,
> > and 63 to
> > +16384 bytes for TLS 1.3. The lower minimum for TLS 1.3 accounts
> > for the
> > +extra byte used by the ContentType field.
> > +
> > +For TLS 1.3, getsockopt() will return the total plaintext fragment
> > length,
> > +inclusive of the ContentType field.
> > +
> > +[1] https://datatracker.ietf.org/doc/html/rfc8449
> > +
> > Statistics
> > ==========
>
> ...
next prev parent reply other threads:[~2025-10-21 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 9:29 Wilfred Mallawa
2025-10-21 9:29 ` [PATCH net-next v7 2/2] selftests: tls: add tls record_size_limit test Wilfred Mallawa
2025-10-21 11:35 ` [PATCH net-next v7 1/2] net/tls: support setting the maximum payload size Simon Horman
2025-10-21 23:23 ` Wilfred Mallawa [this message]
2025-10-21 12:44 ` Sabrina Dubroca
2025-10-21 23:31 ` Wilfred Mallawa
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=018f3da122b80b7f1ba28bfd4b813eb8879fce19.camel@wdc.com \
--to=wilfred.mallawa@wdc.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®