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>
Subject: Re: [PATCH v2 0/5] Add filesystem-level encryption tests
Date: Mon, 28 Nov 2016 14:25:46 -0800 [thread overview]
Message-ID: <20161128222546.GA145516@google.com> (raw)
In-Reply-To: <1480371402-12204-1-git-send-email-ebiggers@google.com>
On Mon, Nov 28, 2016 at 02:16:37PM -0800, Eric Biggers wrote:
> 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.
>
Forgot to list a few other changes since v1:
* 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
prev parent reply other threads:[~2016-11-28 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 22:16 [PATCH v2 0/5] Add filesystem-level encryption tests Eric Biggers
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-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 ` Eric Biggers [this message]
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=20161128222546.GA145516@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 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.