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
| ||
|
Message-Id: <20190201.150552.1791072317521400318.davem@davemloft.net> Date: Fri, 01 Feb 2019 15:05:52 -0800 (PST) From: David Miller <davem@...emloft.net> To: davejwatson@...com Cc: netdev@...r.kernel.org, vakul.garg@....com, borisp@...lanox.com, aviadye@...lanox.com, john.fastabend@...il.com, daniel@...earbox.net Subject: Re: [PATCH net-next] net: tls: Set async_capable for tls zerocopy only if we see EINPROGRESS From: Dave Watson <davejwatson@...com> Date: Wed, 30 Jan 2019 22:08:21 +0000 > Currently we don't zerocopy if the crypto framework async bit is set. > However some crypto algorithms (such as x86 AESNI) support async, > but in the context of sendmsg, will never run asynchronously. Instead, > check for actual EINPROGRESS return code before assuming algorithm is > async. > > Signed-off-by: Dave Watson <davejwatson@...com> Applied, thanks.
Powered by blists - more mailing lists