From: Eric Biggers <ebiggers@kernel.org> To: linux-fscrypt@vger.kernel.org Cc: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, Satya Tangirala <satyat@google.com>, Paul Crowley <paulcrowley@google.com>, Paul Lawrence <paullawrence@google.com>, "Theodore Y . Ts'o" <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org> Subject: [PATCH v2 0/3] fscrypt: support for IV_INO_LBLK_64 policies Date: Thu, 24 Oct 2019 14:54:35 -0700 [thread overview] Message-ID: <20191024215438.138489-1-ebiggers@kernel.org> (raw) 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(-) -- 2.24.0.rc0.303.g954a862665-goog
WARNING: multiple messages have this Message-ID (diff)
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: [f2fs-dev] [PATCH v2 0/3] fscrypt: support for IV_INO_LBLK_64 policies Date: Thu, 24 Oct 2019 14:54:35 -0700 [thread overview] Message-ID: <20191024215438.138489-1-ebiggers@kernel.org> (raw) 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(-) -- 2.24.0.rc0.303.g954a862665-goog _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2019-10-24 21:57 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-24 21:54 Eric Biggers [this message] 2019-10-24 21:54 ` [f2fs-dev] [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-24 21:54 ` [f2fs-dev] " Eric Biggers 2019-10-29 17:47 ` Paul Crowley 2019-10-29 17:47 ` [f2fs-dev] " Paul Crowley via Linux-f2fs-devel 2019-11-06 3:35 ` Theodore Y. Ts'o 2019-11-06 3:35 ` [f2fs-dev] " Theodore Y. Ts'o 2019-11-06 4:05 ` Eric Biggers 2019-11-06 4:05 ` [f2fs-dev] " Eric Biggers 2019-11-07 2:49 ` Theodore Y. Ts'o 2019-11-07 2:49 ` [f2fs-dev] " 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-10-24 21:54 ` [f2fs-dev] " Eric Biggers 2019-11-06 3:26 ` Theodore Y. Ts'o 2019-11-06 3:26 ` [f2fs-dev] " Theodore Y. Ts'o 2019-10-24 21:54 ` [PATCH v2 3/3] f2fs: " Eric Biggers 2019-10-24 21:54 ` [f2fs-dev] " Eric Biggers 2019-11-01 18:33 ` Jaegeuk Kim 2019-11-01 18:33 ` [f2fs-dev] " Jaegeuk Kim 2019-11-01 18:02 ` [PATCH v2 0/3] fscrypt: support for IV_INO_LBLK_64 policies Eric Biggers 2019-11-01 18:02 ` [f2fs-dev] " Eric Biggers 2019-11-06 21:04 ` Eric Biggers 2019-11-06 21:04 ` [f2fs-dev] " Eric Biggers
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=20191024215438.138489-1-ebiggers@kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.