From: Eric Biggers <ebiggers@google.com>
To: fstests@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>,
Richard Weinberger <richard@nod.at>,
David Gstir <david@sigma-star.at>,
Michael Halcrow <mhalcrow@google.com>,
Eric Biggers <ebiggers@google.com>
Subject: [PATCH v2 0/5] Add filesystem-level encryption tests
Date: Mon, 28 Nov 2016 14:16:37 -0800 [thread overview]
Message-ID: <1480371402-12204-1-git-send-email-ebiggers@google.com> (raw)
This is the second version of the patch series to add some xfstests for
filesystem-level encryption. The new tests are designed to run on any
filesystem that implements the "fscrypt" API, currently ext4 and f2fs. (fscrypt
support for ubifs is also under development, but it looks like xfstests doesn't
have ubifs support yet.)
The new tests are designed to complement, not replace, doing a full xfstests run
with encryption enabled, which for ext4 can currently be done by using the
test_dummy_encryption mount option.
v2 of the series drops the fscrypt_util test program and instead uses new xfs_io
commands to set and get encryption policies, and uses keyctl to add and remove
encryption keys. I'm sending the xfs_io patch separately since xfs_io is part
of xfsprogs.
Eric Biggers (5):
generic: add utilities for testing filesystem encryption
generic: test setting and getting encryption policies
generic: test validation of encryption policy structure
generic: test encrypted file access
generic: test for weaknesses in filesystem encryption
common/config | 2 +
common/encrypt | 128 +++++++++++++++++++++++++++++++++++++++++
tests/generic/400 | 126 ++++++++++++++++++++++++++++++++++++++++
tests/generic/400.out | 43 ++++++++++++++
tests/generic/401 | 83 +++++++++++++++++++++++++++
tests/generic/401.out | 18 ++++++
tests/generic/402 | 145 ++++++++++++++++++++++++++++++++++++++++++++++
tests/generic/402.out | 11 ++++
tests/generic/403 | 155 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/generic/403.out | 3 +
tests/generic/group | 4 ++
11 files changed, 718 insertions(+)
create mode 100644 common/encrypt
create mode 100755 tests/generic/400
create mode 100644 tests/generic/400.out
create mode 100755 tests/generic/401
create mode 100644 tests/generic/401.out
create mode 100755 tests/generic/402
create mode 100644 tests/generic/402.out
create mode 100755 tests/generic/403
create mode 100644 tests/generic/403.out
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-11-28 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 22:16 Eric Biggers [this message]
2016-11-28 22:16 ` [PATCH v2 1/5] generic: add utilities for testing filesystem encryption Eric Biggers
2016-11-28 22:16 ` [PATCH v2 2/5] generic: test setting and getting encryption policies Eric Biggers
2016-11-28 22:16 ` [PATCH v2 3/5] generic: test validation of encryption policy structure Eric Biggers
2016-11-28 22:16 ` [PATCH v2 4/5] generic: test encrypted file access Eric Biggers
2016-11-29 20:52 ` Richard Weinberger
2016-12-01 0:30 ` Eric Biggers
2016-11-28 22:16 ` [PATCH v2 5/5] generic: test for weaknesses in filesystem encryption Eric Biggers
2016-11-28 22:25 ` [PATCH v2 0/5] Add filesystem-level encryption tests 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=1480371402-12204-1-git-send-email-ebiggers@google.com \
--to=ebiggers@google.com \
--cc=david@sigma-star.at \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=mhalcrow@google.com \
--cc=richard@nod.at \
--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