Re: [PATCH net-next] docs: tls: Enhance TLS resync async process documentation

[Bagas Sanjaya <bagasdotme@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]

On Tue, Nov 25, 2025 at 09:00:37AM +0200, Tariq Toukan wrote:
> +When the kernel processes an RX segment that begins a new TLS record, it
> +examines the current status of the asynchronous resynchronization request.
> +- If the device is still waiting to provide its guessed TCP sequence number
> +  (the async state), the kernel records the sequence number of this segment
> +  so that it can later be compared once the device's guess becomes available.
> +- If the device has already submitted its guessed sequence number (the non-async
> +  state), the kernel now tries to match that guess against the sequence numbers
> +  of all TLS record headers that have been logged since the resync request
> +  started.
> +

You need to separate the status list:

---- >8 ----
diff --git a/Documentation/networking/tls-offload.rst b/Documentation/networking/tls-offload.rst
index 6d276931669979..a41d02d72e1ee6 100644
--- a/Documentation/networking/tls-offload.rst
+++ b/Documentation/networking/tls-offload.rst
@@ -338,6 +338,7 @@ Cancels any in-progress resync attempt, clearing the request state.
 
 When the kernel processes an RX segment that begins a new TLS record, it
 examines the current status of the asynchronous resynchronization request.
+
 - If the device is still waiting to provide its guessed TCP sequence number
   (the async state), the kernel records the sequence number of this segment
   so that it can later be compared once the device's guess becomes available.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]