From: Eric Biggers <ebiggers3@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, 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 Sandeen <sandeen@redhat.com>,
Eric Biggers <ebiggers@google.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v4 6/6] generic: test for weaknesses in filesystem encryption
Date: Wed, 21 Dec 2016 13:36:01 -0800 [thread overview]
Message-ID: <20161221213601.GB136777@gmail.com> (raw)
In-Reply-To: <20161219072628.GC1859@eguan.usersys.redhat.com>
On Mon, Dec 19, 2016 at 03:26:28PM +0800, Eryu Guan wrote:
>
> Can you please send an updated patch 6/6? Otherwise the whole series
> look good to me! I'm going to let the patchset sit in the list for
> another week and push them out to upstream in next fstests update, if
> there's no further comments from others.
>
> Thanks,
> Eryu
I just changed patch 6/6 but I went ahead and sent out v5 of the series so that
people don't mix up the different patches.
+Cc linux-xfs@vger.kernel.org
Also, would it be possible to get the xfs_io patch merged into xfsprogs at about
the same time? Ultimately, both the xfstests and xfsprogs changes are needed to
run the new tests; without the xfsprogs change they'll all be skipped.
Thanks,
Eric
prev parent reply other threads:[~2016-12-21 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 20:26 [PATCH v4 0/6] Add filesystem-level encryption tests Eric Biggers
2016-12-15 20:26 ` [PATCH v4 1/6] generic: add utilities for testing filesystem encryption Eric Biggers
2016-12-15 20:26 ` [PATCH v4 2/6] generic: test setting and getting encryption policies Eric Biggers
2016-12-15 20:26 ` [PATCH v4 3/6] generic: test validation of encryption policy structure Eric Biggers
2016-12-15 20:26 ` [PATCH v4 4/6] generic: test encrypted file access Eric Biggers
2016-12-15 20:26 ` [PATCH v4 5/6] generic: test enforcement of one encryption policy per tree Eric Biggers
2016-12-15 20:26 ` [PATCH v4 6/6] generic: test for weaknesses in filesystem encryption Eric Biggers
2016-12-19 7:26 ` Eryu Guan
2016-12-21 21:36 ` 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=20161221213601.GB136777@gmail.com \
--to=ebiggers3@gmail.com \
--cc=david@sigma-star.at \
--cc=ebiggers@google.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mhalcrow@google.com \
--cc=richard@nod.at \
--cc=sandeen@redhat.com \
--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