netdev - Re: pull-request: mlx5-next 2023-01-24 V2

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] [day] [month] [year] [list]

Message-ID: <Y+Z7lVVWqnRBiPh2@nvidia.com>
Date:   Fri, 10 Feb 2023 13:15:01 -0400
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Saeed Mahameed <saeed@...nel.org>,
        Leon Romanovsky <leon@...nel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Paolo Abeni <pabeni@...hat.com>,
        Eric Dumazet <edumazet@...gle.com>,
        Saeed Mahameed <saeedm@...dia.com>, linux-rdma@...r.kernel.org,
        netdev@...r.kernel.org
Subject: Re: pull-request: mlx5-next 2023-01-24 V2

On Wed, Feb 08, 2023 at 05:16:46PM -0800, Jakub Kicinski wrote:
> On Wed, 8 Feb 2023 20:59:59 -0400 Jason Gunthorpe wrote:
> > > Who said IP configuration.  
> > 
> > Please explain to me your vision how we could do IPSEC in rdma and
> > continue to use an IP address owned by netdev while netdev is also
> > running IPSEC on the same IP address for netdev traffic.
> 
> I'm no expert on IPsec but AFAIK it doesn't treat the entire endpoint
> as a single unit.

It does, the SA #'s in the ESP header have to be globally allocated.
 
> Could you please go back to answering the question of how we deliver
> on the compromise that was established to merge the full xfrm offload?

I've said repeatedly it is in our plans, we have people working on it,
and I'm not allowed to commit to specific dates in public.

Jason