From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org
Subject: [PATCH v2 0/3] xfstests: test adding filesystem-level fscrypt key via key_id
Date: Mon, 3 Feb 2020 10:18:52 -0800 [thread overview]
Message-ID: <20200203181855.42987-1-ebiggers@kernel.org> (raw)
This series adds a test which tests adding a key to a filesystem's
fscrypt keyring via an "fscrypt-provisioning" keyring key. This is an
alternative to the normal method where the raw key is given directly.
The needed kernel support was merged in 5.6, so currently this test
needs the latest mainline kernel to run.
This test also depends on an xfs_io patch which adds the '-k' option to
the 'add_enckey' command, e.g.:
xfs_io -c "add_enckey -k KEY_ID" MOUNTPOINT
This test is skipped if the needed kernel or xfs_io support is absent.
This has been tested on ext4, f2fs, and ubifs.
This series can also be retrieved from
https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/xfstests-dev.git
tag "fscrypt-provisioning_2020-02-03".
Changed since v1:
- Fixed incorrect detection of kernel support.
Eric Biggers (3):
common/rc: handle option with argument in _require_xfs_io_command()
common/encrypt: move constant test key to common code
generic: test adding filesystem-level fscrypt key via key_id
common/encrypt | 95 ++++++++++++++++++++++----
common/rc | 2 +-
tests/generic/580 | 17 ++---
tests/generic/806 | 155 ++++++++++++++++++++++++++++++++++++++++++
tests/generic/806.out | 73 ++++++++++++++++++++
tests/generic/group | 1 +
6 files changed, 315 insertions(+), 28 deletions(-)
create mode 100644 tests/generic/806
create mode 100644 tests/generic/806.out
--
2.25.0.341.g760bfbb309-goog
next reply other threads:[~2020-02-03 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 18:18 Eric Biggers [this message]
2020-02-03 18:18 ` [PATCH v2 1/3] common/rc: handle option with argument in _require_xfs_io_command() Eric Biggers
2020-02-03 18:18 ` [PATCH v2 2/3] common/encrypt: move constant test key to common code Eric Biggers
2020-02-03 18:18 ` [PATCH v2 3/3] generic: test adding filesystem-level fscrypt key via key_id 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=20200203181855.42987-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
/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).