netdev - Re: [PATCH ipsec v3 0/4] Support IPsec crypto offload for IPv6 ESP and IPv4 UDP-encapsulated ESP data paths

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: <Zo+vx4wS49TNX4fa@gauss3.secunet.de>
Date: Thu, 11 Jul 2024 12:11:19 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Leon Romanovsky <leon@...nel.org>
CC: Mike Yu <yumike@...gle.com>, <netdev@...r.kernel.org>,
	<stanleyjhu@...gle.com>, <martinwu@...gle.com>, <chiachangwang@...gle.com>
Subject: Re: [PATCH ipsec v3 0/4] Support IPsec crypto offload for IPv6 ESP
 and IPv4 UDP-encapsulated ESP data paths

On Thu, Jul 11, 2024 at 12:52:08PM +0300, Leon Romanovsky wrote:
> On Wed, Jul 10, 2024 at 07:16:50PM +0800, Mike Yu wrote:
> > 
> > Mike Yu (4):
> >   xfrm: Support crypto offload for inbound IPv6 ESP packets not in GRO
> >     path
> >   xfrm: Allow UDP encapsulation in crypto offload control path
> >   xfrm: Support crypto offload for inbound IPv4 UDP-encapsulated ESP
> >     packet
> >   xfrm: Support crypto offload for outbound IPv4 UDP-encapsulated ESP
> >     packet
> > 
> >  net/ipv4/esp4.c         |  8 +++++++-
> >  net/ipv4/esp4_offload.c | 17 ++++++++++++++++-
> >  net/xfrm/xfrm_device.c  |  6 +++---
> >  net/xfrm/xfrm_input.c   |  3 ++-
> >  net/xfrm/xfrm_policy.c  |  5 ++++-
> >  5 files changed, 32 insertions(+), 7 deletions(-)
> 
> Steffen,
> 
> If it helps, we tested v2 version and it didn't break anything for us :).
> But we didn't test this specific functionality.
> 
> Thanks

Thanks for testing it Leon!

This is a new feature, so I don't want to apply it to the ipsec
tree. Mike, can you rebase on top of ipsec-next instead?

Thanks!