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
| ||
|
Date: Fri, 1 May 2020 12:30:21 +0200 From: Greg KH <gregkh@...uxfoundation.org> To: Rajan Vaja <rajan.vaja@...inx.com> Cc: herbert@...dor.apana.org.au, davem@...emloft.net, kalyani.akula@...inx.com, michal.simek@...inx.com, jolly.shah@...inx.com, linux-crypto@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH char-misc-next] crypto: xilinx: Handle AES PM API return status On Fri, May 01, 2020 at 03:14:51AM -0700, Rajan Vaja wrote: > Fixes: bc86f9c54616 ("firmware: xilinx: Remove eemi ops for aes engine") > > Return value of AES PM API is not handled which may result in > unexpected value of "status" in zynqmp_pm_aes_engine(). > > Consider "status" value as valid only if AES PM API is successful. > > Signed-off-by: Rajan Vaja <rajan.vaja@...inx.com> No "Reported-by:" line? And put the "Fixes:" line down in the s-o-b area please. thanks, greg k-h
Powered by blists - more mailing lists