netdev - Re: [PATCH net-next v2 6/8] Documentation: xfrm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6a336251-109a-4843-b68c-88ca93fb501d@infradead.org>
Date: Sat, 1 Nov 2025 11:56:56 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Bagas Sanjaya <bagasdotme@...il.com>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Documentation <linux-doc@...r.kernel.org>,
 Linux Networking <netdev@...r.kernel.org>
Cc: "David S. Miller" <davem@...emloft.net>,
 Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
 Jonathan Corbet <corbet@....net>,
 Steffen Klassert <steffen.klassert@...unet.com>,
 Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [PATCH net-next v2 6/8] Documentation: xfrm_sync: Number the
 fifth section

On 11/1/25 2:47 AM, Bagas Sanjaya wrote:
> Number the fifth section ("Exception to threshold settings") to be
> consistent with the rest of sections.
> 
> Suggested-by: Randy Dunlap <rdunlap@...radead.org>
> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>

Reviewed-by: Randy Dunlap <rdunlap@...radead.org>
Tested-by: Randy Dunlap <rdunlap@...radead.org>

> ---
>  Documentation/networking/xfrm_sync.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/networking/xfrm_sync.rst b/Documentation/networking/xfrm_sync.rst
> index de4da4707037ea..112f7c102ad043 100644
> --- a/Documentation/networking/xfrm_sync.rst
> +++ b/Documentation/networking/xfrm_sync.rst
> @@ -179,8 +179,8 @@ happened) is set to inform the user what happened.
>  Note the two flags are mutually exclusive.
>  The message will always have XFRMA_LTIME_VAL and XFRMA_REPLAY_VAL TLVs.
>  
> -Exceptions to threshold settings
> ---------------------------------
> +5) Exceptions to threshold settings
> +-----------------------------------
>  
>  If you have an SA that is getting hit by traffic in bursts such that
>  there is a period where the timer threshold expires with no packets

-- 
~Randy