From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org, Satya Tangirala <satyat@google.com>
Subject: [PATCH v2 0/5] xfstests: verify ciphertext of IV_INO_LBLK_64 encryption policies
Date: Mon, 2 Dec 2019 15:01:50 -0800 [thread overview]
Message-ID: <20191202230155.99071-1-ebiggers@kernel.org> (raw)
Hello,
This series adds an xfstest which tests that the encryption for
IV_INO_LBLK_64 encryption policies is being done correctly.
IV_INO_LBLK_64 is 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. For
more information, see the kernel patchset:
https://lore.kernel.org/linux-fscrypt/20191024215438.138489-1-ebiggers@kernel.org/T/#u
The kernel patches have been merged into mainline and will be in v5.5.
In addition to the latest kernel, to run on ext4 this test also needs a
version of e2fsprogs built from the master branch, in order to get
support for formatting the filesystem with '-O stable_inodes'.
As usual, the test will skip itself if the prerequisites aren't met.
No real changes since v1; just rebased onto the latest xfstests master
branch and updated the cover letter.
Eric Biggers (5):
fscrypt-crypt-util: create key_and_iv_params structure
fscrypt-crypt-util: add HKDF context constants
common/encrypt: create named variables for UAPI constants
common/encrypt: support verifying ciphertext of IV_INO_LBLK_64
policies
generic: verify ciphertext of IV_INO_LBLK_64 encryption policies
common/encrypt | 126 +++++++++++++++++++++++++-------
src/fscrypt-crypt-util.c | 151 ++++++++++++++++++++++++++++-----------
tests/generic/805 | 43 +++++++++++
tests/generic/805.out | 6 ++
tests/generic/group | 1 +
5 files changed, 259 insertions(+), 68 deletions(-)
create mode 100644 tests/generic/805
create mode 100644 tests/generic/805.out
--
2.24.0.393.g34dc348eaf-goog
next reply other threads:[~2019-12-02 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 23:01 Eric Biggers [this message]
2019-12-02 23:01 ` [PATCH v2 1/5] fscrypt-crypt-util: create key_and_iv_params structure Eric Biggers
2019-12-02 23:01 ` [PATCH v2 2/5] fscrypt-crypt-util: add HKDF context constants Eric Biggers
2019-12-02 23:01 ` [PATCH v2 3/5] common/encrypt: create named variables for UAPI constants Eric Biggers
2019-12-02 23:01 ` [PATCH v2 4/5] common/encrypt: support verifying ciphertext of IV_INO_LBLK_64 policies Eric Biggers
2019-12-02 23:01 ` [PATCH v2 5/5] generic: verify ciphertext of IV_INO_LBLK_64 encryption policies Eric Biggers
2019-12-09 18:18 ` [PATCH v2 0/5] xfstests: " Eric Biggers
2020-01-03 16:46 ` Eric Biggers
2020-01-06 2:55 ` Eryu Guan
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=20191202230155.99071-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=satyat@google.com \
/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).