From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EC6EEC0044B for ; Wed, 13 Feb 2019 20:21:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C105C21872 for ; Wed, 13 Feb 2019 20:21:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729933AbfBMUVu (ORCPT ); Wed, 13 Feb 2019 15:21:50 -0500 Received: from ipmail07.adl2.internode.on.net ([150.101.137.131]:12185 "EHLO ipmail07.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728066AbfBMUVu (ORCPT ); Wed, 13 Feb 2019 15:21:50 -0500 Received: from ppp59-167-129-252.static.internode.on.net (HELO dastard) ([59.167.129.252]) by ipmail07.adl2.internode.on.net with ESMTP; 14 Feb 2019 06:51:49 +1030 Received: from dave by dastard with local (Exim 4.80) (envelope-from ) id 1gu12R-00055k-Cg; Thu, 14 Feb 2019 07:21:47 +1100 Date: Thu, 14 Feb 2019 07:21:47 +1100 From: Dave Chinner To: Dave Hansen Cc: Dan Williams , lsf-pc@lists.linux-foundation.org, linux-fsdevel , Linux-MM , "Shutemov, Kirill" , "Schofield, Alison" , "Darrick J. Wong" , Jan Kara , Christoph Hellwig , Theodore Ts'o , Jaegeuk Kim Subject: Re: [LSF/MM TOPIC] Memory Encryption on top of filesystems Message-ID: <20190213202147.GP20493@dastard> References: <788d7050-f6bb-b984-69d9-504056e6c5a6@intel.com> <20190212235114.GM20493@dastard> <20190213021318.GN20493@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Wed, Feb 13, 2019 at 07:51:12AM -0800, Dave Hansen wrote: > On 2/12/19 7:31 PM, Dan Williams wrote: > > Thanks, yes, fscrypt needs a closer look. As far I can see at a quick > > glance fscrypt has the same physical block inputs for the encryption > > algorithm as MKTME so it seems it could be crafted as a drop in > > accelerator for fscrypt for pmem block devices. > > One bummer is that we have the platform tweak offsets to worry about. What's a "platform tweak offset"? > As far as I know, those are opaque to software and practically prevent > us from replicating the MKTME hardware's encryption/decryption in software. We're not trying to replicate the encryption in software, just use the existing software to manage the keys that get fed to the hardware so it can do the encrypt/decrypt operations as the data passes through it. Cheers, Dave. -- Dave Chinner david@fromorbit.com