netdev - Re: [PATCH 0/12] pull request (net-next): ipsec-next 2025-05-23

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: <aDBPkpKv+x7YFDWJ@gauss3.secunet.de>
Date: Fri, 23 May 2025 12:36:02 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: David Miller <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>
CC: Herbert Xu <herbert@...dor.apana.org.au>, <netdev@...r.kernel.org>
Subject: Re: [PATCH 0/12] pull request (net-next): ipsec-next 2025-05-23

On Fri, May 23, 2025 at 09:55:59AM +0200, Steffen Klassert wrote:
> 1) Remove some unnecessary strscpy_pad() size arguments.
>    From Thorsten Blum.
> 
> 2) Correct use of xso.real_dev on bonding offloads.
>    Patchset from Cosmin Ratiu.
> 
> 3) Add hardware offload configuration to XFRM_MSG_MIGRATE.
>    From Chiachang Wang.
> 
> 4) Refactor migration setup during cloning. This was
>    done after the clone was created. Now it is done
>    in the cloning function itself.
>    From Chiachang Wang.
> 
> 5) Validate assignment of maximal possible SEQ number.
>    Prevent from setting to the maximum sequrnce number
>    as this would cause for traffic drop.
>    From Leon Romanovsky.
> 
> 6) Prevent configuration of interface index when offload
>    is used. Hardware can't handle this case.i
>    From Leon Romanovsky.
> 
> 7) Always use kfree_sensitive() for SA secret zeroization.
>    From Zilin Guan.
> 
> Please pull or let me know if there are problems.
> 
> Thanks!

I forgot to mention a merge conflict between

 fd5ef5203ce6 ("ixgbe: wrap netdev_priv() usage")

from the net-next tree and commit:

  43eca05b6a3b ("xfrm: Add explicit dev to .xdo_dev_state_{add,delete,free}")

from the ipsec-next tree.

It can be solved as done in linux-next.

Thanks!