[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 11 Dec 2018 23:40:17 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Parshuram Raju Thombare <pthombar@...ence.com>
Cc: Christoph Hellwig <hch@...radead.org>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"vinholikatti@...il.com" <vinholikatti@...il.com>,
"jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"mchehab+samsung@...nel.org" <mchehab+samsung@...nel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"nicolas.ferre@...rochip.com" <nicolas.ferre@...rochip.com>,
"arnd@...db.de" <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"tj@...nel.org" <tj@...nel.org>, "jbacik@...com" <jbacik@...com>,
"michaelcallahan@...com" <michaelcallahan@...com>,
"snitzer@...hat.com" <snitzer@...hat.com>,
"osandov@...com" <osandov@...com>,
"keith.busch@...el.com" <keith.busch@...el.com>,
"ming.lei@...hat.com" <ming.lei@...hat.com>,
"shli@...com" <shli@...com>,
"dennisszhou@...il.com" <dennisszhou@...il.com>,
Alan Douglas <adouglas@...ence.com>,
Janek Kotas <jank@...ence.com>,
Rafal Ciepiela <rafalc@...ence.com>
Subject: Re: [PATCH 0/2] scsi: ufs: add real time/inline crypto support to
UFS HCD
On Tue, Dec 11, 2018 at 06:22:27PM +0000, Parshuram Raju Thombare wrote:
> One reason of using device mapper here is to use existing tools like
> 'dmsetup', otherwise some user space application is needed and may be
> some changes in block layer to pass the crypto information (crypto
> algorithm, key etc) till ufs driver.
Yes, so what? We also don't use dmsetup to set up TCG OPAL based
encryption either.
> Another reason is supporting multiple UFS devices. I think, as you said
> UFS crypto support can be added by some change in ufs driver and block
> layer glue. But to support multiple UFS crypto devices having different
> crypto configs (crypto algorithms, key size etc), crypto context need to
> be saved per crypto device which may need some changes in block layer code.
I don't think we need device mapper for that. We can hav the crypto
state hanging off the ufs host, or request_queue if we decide to
implement it generic in the block layer.
Powered by blists - more mailing lists