netdev - Re: [PATCH 0/5] pull request (net-next): ipsec-next 2022-07-20

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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 25 Jul 2022 14:23: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/5] pull request (net-next): ipsec-next 2022-07-20

On Wed, Jul 20, 2022 at 10:17:41AM +0200, Steffen Klassert wrote:
> 1) Don't set DST_NOPOLICY in IPv4, a recent patch made this
>    superfluous. From Eyal Birger.
> 
> 2) Convert alg_key to flexible array member to avoid an iproute2
>    compile warning when built with gcc-12.
>    From Stephen Hemminger.
> 
> 3) xfrm_register_km and xfrm_unregister_km do always return 0
>    so change the type to void. From Zhengchao Shao.
> 
> 4) Fix spelling mistake in esp6.c
>    From Zhang Jiaming.
> 
> 5) Improve the wording of comment above XFRM_OFFLOAD flags.
>    From Petr Vaněk.
> 
> Please pull or let me know if there are problems.

Can anyone reconsider this pull request?

It is marked as Accepted in patchwork, but seems not to be included
in net-next.

Thanks!