On Wed, Aug 21, 2019 at 5:10 AM Satya Tangirala <satyat@xxxxxxxxx> wrote: > > Hi Boojin, > > We're very keen to make sure that our approach to inline encryption can > work with diverse hardware, including Samsung's FMP hardware; if you > can see any issues with using our approach with your hardware please > let us know. > > We understand that a possible concern for getting FMP working with our > patch series for Inline Encryption Support at > > https://lore.kernel.org/linux-block/20190821075714.65140-1-satyat@xxxxxxxxxx / > > is that unlike some inline encryption hardware (and also unlike the JEDEC > UFS v2.1 spec), FMP doesn't have the concept of a limited number of > keyslots - to address that difference we have a "passthrough keyslot > manager", which we put up on top of our patch series for inline encryption > support at > > https://android-review.googlesource.com/c/kernel/common/+/980137/2 > > Setting up a passthrough keyslot manager in the request queue of a > device allows the device to receive a bio's encryption context as-is with > the bio, which is what FMP would prefer. Are there any issues with > using the passthrough keyslot manager for FMP? > > Thanks! > Satya Dear Satya. Keyslot manager is a good solution for ICE. And probably no issue for FMP. But, I think it's complicated for FMP because FMP doesn't need any keyslot control. Crypto API that FMP's using is simply, stable, and supports test. FMP has been mass producing and certificating using crypto APIs for several years. So I wants to keep our current crypto API solution. But, I'm looking at your patch. And I will keep examining at your patch because our goal is to run the FMP on the mainline kernel. Thanks for your reply. Boojin Kim.
