linux-kernel - Re: [PATCH v4 01/15] ice, ufs, mmc: use blk_crypto_key for program

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]

Date: Tue, 6 Feb 2024 12:46:52 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
To: Gaurav Kashyap <quic_gaurkash@...cinc.com>
Cc: linux-arm-msm@...r.kernel.org, linux-scsi@...r.kernel.org, 
	andersson@...nel.org, ebiggers@...gle.com, neil.armstrong@...aro.org, 
	srinivas.kandagatla@...aro.org, krzysztof.kozlowski+dt@...aro.org, 
	conor+dt@...nel.org, robh+dt@...nel.org, linux-kernel@...r.kernel.org, 
	linux-mmc@...r.kernel.org, kernel@...cinc.com, linux-crypto@...r.kernel.org, 
	devicetree@...r.kernel.org, quic_omprsing@...cinc.com, 
	quic_nguyenb@...cinc.com, konrad.dybcio@...aro.org, ulf.hansson@...aro.org, 
	jejb@...ux.ibm.com, martin.petersen@...cle.com, mani@...nel.org, 
	davem@...emloft.net, herbert@...dor.apana.org.au
Subject: Re: [PATCH v4 01/15] ice, ufs, mmc: use blk_crypto_key for program_key

On Sun, 28 Jan 2024 at 00:26, Gaurav Kashyap <quic_gaurkash@...cinc.com> wrote:
>
> The program key ops in the storage controller does not
> pass on the blk crypto key structure to ice, this is okay
> when wrapped keys are not supported and keys are standard
> AES XTS sizes. However, wrapped keyblobs can be of any size
> and in preparation for that, modify the ICE and storage
> controller APIs to accept blk_crypto_key.
>
> Signed-off-by: Gaurav Kashyap <quic_gaurkash@...cinc.com>
> Reviewed-by: Om Prakash Singh <quic_omprsing@...cinc.com>
> Tested-by: Neil Armstrong <neil.armstrong@...aro.org>
> ---

Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>