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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 15 May 2020 14:35:26 +0800 From: Stanley Chu <stanley.chu@...iatek.com> To: Satya Tangirala <satyat@...gle.com> CC: <linux-block@...r.kernel.org>, <linux-scsi@...r.kernel.org>, <linux-fscrypt@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>, <linux-f2fs-devel@...ts.sourceforge.net>, <linux-ext4@...r.kernel.org>, "Barani Muthukumaran" <bmuthuku@....qualcomm.com>, Kuohong Wang <kuohong.wang@...iatek.com>, Kim Boojin <boojin.kim@...sung.com>, "Eric Biggers" <ebiggers@...gle.com> Subject: Re: [PATCH v13 07/12] scsi: ufs: UFS crypto API Hi Satya, On Thu, 2020-05-14 at 00:37 +0000, Satya Tangirala wrote: > Introduce functions to manipulate UFS inline encryption hardware > in line with the JEDEC UFSHCI v2.1 specification and to work with the > block keyslot manager. > > The UFS crypto API will assume by default that a vendor driver doesn't > support UFS crypto, even if the hardware advertises the capability, because > a lot of hardware requires some special handling that's not specified in > the aforementioned JEDEC spec. Each vendor driver must explicity set explicitly > hba->caps |= UFSHCD_CAP_CRYPTO before ufshcd_hba_init_crypto is called to > opt-in to UFS crypto support. > > Signed-off-by: Satya Tangirala <satyat@...gle.com> > Reviewed-by: Eric Biggers <ebiggers@...gle.com> Reviewed-by: Stanley Chu <stanley.chu@...iatek.com>
Powered by blists - more mailing lists