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 v3 0/6] Add filesystem-level encryption tests
Date: Mon, 5 Dec 2016 11:21:03 -0800 [thread overview]
Message-ID: <1480965669-39714-1-git-send-email-ebiggers@google.com> (raw)
This is the third 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.
Changes since v2:
* Use filesystem-specific key prefix rather than generic one.
* Use a new keyring for each test.
* Add a test for restrictions on moving and linking files.
* Make "cryptographic weaknesses" test compatible with f2fs.
* For now, accept both the old and new versions of certain error
codes which are planned to be changed.
Changes since v1:
* Drop fscrypt_util test program and use new xfs_io commands and
keyctl instead (xfs_io patch sent separately)
* Updates to match xfstests coding style
* Move validation of policy structure into its own test
* Add test to detect some cryptographic weaknesses
* Drop ioctl locking test
Eric Biggers (6):
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 enforcement of one encryption policy per tree
generic: test for weaknesses in filesystem encryption
common/config | 2 +
common/encrypt | 137 ++++++++++++++++++++++++++++++++++++++++++
tests/generic/400 | 132 ++++++++++++++++++++++++++++++++++++++++
tests/generic/400.out | 43 +++++++++++++
tests/generic/401 | 83 +++++++++++++++++++++++++
tests/generic/401.out | 18 ++++++
tests/generic/402 | 145 ++++++++++++++++++++++++++++++++++++++++++++
tests/generic/402.out | 13 ++++
tests/generic/403 | 130 ++++++++++++++++++++++++++++++++++++++++
tests/generic/403.out | 34 +++++++++++
tests/generic/404 | 163 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/generic/404.out | 3 +
tests/generic/group | 5 ++
13 files changed, 908 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 100644 tests/generic/403
create mode 100644 tests/generic/403.out
create mode 100755 tests/generic/404
create mode 100644 tests/generic/404.out
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-12-05 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 19:21 Eric Biggers [this message]
2016-12-05 19:21 ` [PATCH v3 1/6] generic: add utilities for testing filesystem encryption Eric Biggers
2016-12-13 5:41 ` Eryu Guan
2016-12-13 7:05 ` Darrick J. Wong
2016-12-05 19:21 ` [PATCH v3 2/6] generic: test setting and getting encryption policies Eric Biggers
2016-12-13 5:59 ` Eryu Guan
2016-12-05 19:21 ` [PATCH v3 3/6] generic: test validation of encryption policy structure Eric Biggers
2016-12-05 19:21 ` [PATCH v3 4/6] generic: test encrypted file access Eric Biggers
2016-12-05 19:21 ` [PATCH v3 5/6] generic: test enforcement of one encryption policy per tree Eric Biggers
2016-12-13 6:07 ` Eryu Guan
2016-12-05 19:21 ` [PATCH v3 6/6] generic: test for weaknesses in filesystem encryption Eric Biggers
2016-12-13 6:12 ` [PATCH v3 0/6] Add filesystem-level encryption tests Eryu Guan
2016-12-15 0:31 ` 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=1480965669-39714-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