netdev - Re: [pull request][net-next 00/15] mlx5 tls rx offload 2020-06-26

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: <20200629.172447.1129902296805016837.davem@davemloft.net>
Date:   Mon, 29 Jun 2020 17:24:47 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     saeedm@...lanox.com
Cc:     kuba@...nel.org, netdev@...r.kernel.org
Subject: Re: [pull request][net-next 00/15] mlx5 tls rx offload 2020-06-26

From: Saeed Mahameed <saeedm@...lanox.com>
Date: Sat, 27 Jun 2020 14:17:12 -0700

> This is a re-spin of the previous kernel cycle mlx5 rx tls submission, From Tariq
> and Boris.
> 
> Changes from previous iteration:
> 1) Better handling of error flows in the resyc procedure.
> 2) An improved TLS device API for Asynchronous Resync to replace "force resync"
> For this Tariq and Boris revert the old "force resync" API then add the new one,
> patch: ('Revert "net/tls: Add force_resync for driver resync"')
> Since there are no users for the "force resync" API it might be a good idea to also
> take this patch to net.
> 
> For more information please see tag log below.
> 
> Please pull and let me know if there is any problem.
> 
> Please note that the series starts with a merge of mlx5-next branch,
> to resolve and avoid dependency with rdma tree.

Pulled, thanks Saeed.