From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Satya Tangirala <satyat@google.com>,
Paul Lawrence <paullawrence@google.com>,
linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org, Paul Crowley <paulcrowley@google.com>
Subject: Re: [PATCH v2 0/3] fscrypt: support for IV_INO_LBLK_64 policies
Date: Wed, 6 Nov 2019 13:04:33 -0800 [thread overview]
Message-ID: <20191106210432.GB139580@gmail.com> (raw)
In-Reply-To: <20191024215438.138489-1-ebiggers@kernel.org>
On Thu, Oct 24, 2019 at 02:54:35PM -0700, Eric Biggers wrote:
> Hello,
>
> In preparation for adding inline encryption support to fscrypt, this
> patchset adds a new fscrypt policy flag which modifies the encryption to
> be optimized for inline encryption hardware compliant with the UFS v2.1
> standard or the upcoming version of the eMMC standard.
>
> This means using per-mode keys instead of per-file keys, and in
> compensation including the inode number in the IVs. For ext4, this
> precludes filesystem shrinking, so I've also added a compat feature
> which will prevent the filesystem from being shrunk.
>
> I've separated this from the full "Inline Encryption Support" patchset
> (https://lkml.kernel.org/linux-fsdevel/20190821075714.65140-1-satyat@google.com/)
> to avoid conflating an implementation (inline encryption) with a new
> on-disk format (IV_INO_LBLK_64). This patchset purely adds support for
> IV_INO_LBLK_64 policies to fscrypt, but implements them using the
> existing filesystem layer crypto.
>
> We're planning to make the *implementation* (filesystem layer or inline
> crypto) be controlled by a mount option '-o inlinecrypt'.
>
> This patchset applies to fscrypt.git#master and can also be retrieved from
> https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=inline-crypt-optimized-v2
>
> I've written a ciphertext verification test for this new type of policy:
> https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/xfstests-dev.git/log/?h=inline-encryption
>
> Work-in-progress patches for the inline encryption implementation of
> both IV_INO_LBLK_64 and regular policies can be found at
> https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=inline-encryption-wip
>
> Changes v1 => v2:
>
> - Rename the flag from INLINE_CRYPT_OPTIMIZED to IV_INO_LBLK_64.
>
> - Use the same key derivation and IV generation scheme for filenames
> encryption too.
>
> - Improve the documentation and commit messages.
>
> Eric Biggers (3):
> fscrypt: add support for IV_INO_LBLK_64 policies
> ext4: add support for IV_INO_LBLK_64 encryption policies
> f2fs: add support for IV_INO_LBLK_64 encryption policies
>
> Documentation/filesystems/fscrypt.rst | 63 +++++++++++++++++----------
> fs/crypto/crypto.c | 10 ++++-
> fs/crypto/fscrypt_private.h | 16 +++++--
> fs/crypto/keyring.c | 6 ++-
> fs/crypto/keysetup.c | 45 ++++++++++++++-----
> fs/crypto/policy.c | 41 ++++++++++++++++-
> fs/ext4/ext4.h | 2 +
> fs/ext4/super.c | 14 ++++++
> fs/f2fs/super.c | 26 ++++++++---
> include/linux/fscrypt.h | 3 ++
> include/uapi/linux/fscrypt.h | 3 +-
> 11 files changed, 182 insertions(+), 47 deletions(-)
>
> --
Applied to fscrypt.git#master for 5.5.
- Eric
prev parent reply other threads:[~2019-11-06 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 21:54 [PATCH v2 0/3] fscrypt: support for IV_INO_LBLK_64 policies Eric Biggers
2019-10-24 21:54 ` [PATCH v2 1/3] fscrypt: add " Eric Biggers
2019-10-29 17:47 ` Paul Crowley
2019-11-06 3:35 ` Theodore Y. Ts'o
2019-11-06 4:05 ` Eric Biggers
2019-11-07 2:49 ` Theodore Y. Ts'o
2019-10-24 21:54 ` [PATCH v2 2/3] ext4: add support for IV_INO_LBLK_64 encryption policies Eric Biggers
2019-11-06 3:26 ` Theodore Y. Ts'o
2019-10-24 21:54 ` [PATCH v2 3/3] f2fs: " Eric Biggers
2019-11-01 18:33 ` Jaegeuk Kim
2019-11-01 18:02 ` [PATCH v2 0/3] fscrypt: support for IV_INO_LBLK_64 policies Eric Biggers
2019-11-06 21:04 ` Eric Biggers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191106210432.GB139580@gmail.com \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=paulcrowley@google.com \
--cc=paullawrence@google.com \
--cc=satyat@google.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).