netdev - Re: [PATCH xfrm-next v9 0/8] Extend XFRM core to allow packet offload configuration

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: <Y4pEknq2Whbw/Z2S@unreal>
Date:   Fri, 2 Dec 2022 20:31:46 +0200
From:   Leon Romanovsky <leon@...nel.org>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Steffen Klassert <steffen.klassert@...unet.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        netdev@...r.kernel.org, Bharat Bhushan <bbhushan2@...vell.com>
Subject: Re: [PATCH xfrm-next v9 0/8] Extend XFRM core to allow packet
 offload configuration

On Fri, Dec 02, 2022 at 10:10:00AM -0800, Jakub Kicinski wrote:
> On Fri, 2 Dec 2022 20:05:19 +0200 Leon Romanovsky wrote:
> > You won't need to apply and deal with any
> > merge conflicts which can bring our code :).
> 
> FWIW the ipsec tree feeds the netdev tree, there should be no conflicts
> or full release cycle delays. In fact merging the infra in one cycle
> and driver in another seems odd, no?

Not really, it is a matter of trust.

The driver exists https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/log/?h=xfrm-next
and it is a lot of code (28 patches for now) which is more natural for us to route through
traditional path.

If you are not convinced, I can post all these patches to the ML right now
and Steffen will send them to you.

Thanks