From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-f66.google.com ([209.85.166.66]:43434 "EHLO mail-io1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728115AbeLMTme (ORCPT ); Thu, 13 Dec 2018 14:42:34 -0500 Received: by mail-io1-f66.google.com with SMTP id l3so2542862ioc.10 for ; Thu, 13 Dec 2018 11:42:33 -0800 (PST) Subject: Re: [PATCH 2/2] scsi: ufs: add inline crypto support to UFS HCD To: Ladvine D Almeida , Parshuram Raju Thombare , Eric Biggers Cc: "vinholikatti@gmail.com" , "jejb@linux.vnet.ibm.com" , "martin.petersen@oracle.com" , "mchehab+samsung@kernel.org" , "gregkh@linuxfoundation.org" , "davem@davemloft.net" , "akpm@linux-foundation.org" , "nicolas.ferre@microchip.com" , "arnd@arndb.de" , "linux-kernel@vger.kernel.org" , "linux-block@vger.kernel.org" , "linux-scsi@vger.kernel.org" , Alan Douglas , Janek Kotas , Rafal Ciepiela , AnilKumar Chimata , Satya Tangirala , Paul Crowley , Manjunath M Bettegowda , Tejas Joglekar , Joao Pinto , "linux-crypto@vger.kernel.org" References: <20181211095027.GA3316@lvlogina.cadence.com> <20181211181647.GC221175@gmail.com> From: Jens Axboe Message-ID: Date: Thu, 13 Dec 2018 12:42:30 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-crypto-owner@vger.kernel.org List-ID: On 12/13/18 12:39 PM, Ladvine D Almeida wrote: > Suggest to take a look into the article https://lwn.net/Articles/717754 > My real concern is how to achieve it without any modifications to the > bio.(because key slot information has to finally reach the target block > device) Guys, you both need to edit when you reply, wading through 650 lines of text to get to this... You obviously can't modify the bio if you don't own it, but you could clone it and then you have storage in ->bi_private. -- Jens Axboe From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: [PATCH 2/2] scsi: ufs: add inline crypto support to UFS HCD Date: Thu, 13 Dec 2018 12:42:30 -0700 Message-ID: References: <20181211095027.GA3316@lvlogina.cadence.com> <20181211181647.GC221175@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Ladvine D Almeida , Parshuram Raju Thombare , Eric Biggers Cc: "vinholikatti@gmail.com" , "jejb@linux.vnet.ibm.com" , "martin.petersen@oracle.com" , "mchehab+samsung@kernel.org" , "gregkh@linuxfoundation.org" , "davem@davemloft.net" , "akpm@linux-foundation.org" , "nicolas.ferre@microchip.com" , "arnd@arndb.de" , "linux-kernel@vger.kernel.org" , "linux-block@vger.kernel.org" , "linux-scsi@vger.kernel.org" , Alan Douglas , Janek Kotas , Rafal Ciepiela , AnilKumar List-Id: linux-scsi@vger.kernel.org On 12/13/18 12:39 PM, Ladvine D Almeida wrote: > Suggest to take a look into the article https://lwn.net/Articles/717754 > My real concern is how to achieve it without any modifications to the > bio.(because key slot information has to finally reach the target block > device) Guys, you both need to edit when you reply, wading through 650 lines of text to get to this... You obviously can't modify the bio if you don't own it, but you could clone it and then you have storage in ->bi_private. -- Jens Axboe