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@infradead.org>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.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