RE: [PATCH v2 8/8] doc: add release note about ip_frag changes

[Konstantin Ananyev <konstantin.ananyev@huawei.com>]

> The changes to ip_frag might impact some conformance or
> performance tests.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  doc/guides/rel_notes/release_26_07.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/release_26_07.rst
> b/doc/guides/rel_notes/release_26_07.rst
> index 4ca0a9ac77..a419803401 100644
> --- a/doc/guides/rel_notes/release_26_07.rst
> +++ b/doc/guides/rel_notes/release_26_07.rst
> @@ -241,6 +241,12 @@ API Changes
>    - ``rte_pmd_mlx5_enable_steering``
>    - ``rte_pmd_mlx5_disable_steering``
> 
> +* **ip_frag: hardened IP reassembly against malformed fragments.**
> +
> +  Duplicate, overlapping, oversized, and (for IPv6) per-fragment-header
> +  fragments are now rejected rather than mis-reassembled. This changes which
> +  fragment streams reassemble and may affect throughput.

That doesn't look entirely correct:
Current implementation doesn't allow both duplicate or overlapping fragments either,
though it postpones it's detection till reassembly stage.
Might be something like that:
**ip_frag: hardened IP reassembly against malformed fragments.**

* Tolerate packets with duplicate fragments,
* Determine duplicate overlapping and oversized fragments at arrival. That change
   can cause multiple extra scans over already received fragments and might affect
   overall system throughput.  
?
 

> +
> 
>  ABI Changes
>  -----------
> --
> 2.53.0