public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH v2] xfstests-bld: populate keyring with default key for test_dummy_encryption
Date: Mon, 30 Jan 2017 15:03:52 -0800	[thread overview]
Message-ID: <20170130230352.GA24293@gmail.com> (raw)
In-Reply-To: <20170130224238.3ez7gcx2wh32xh6o@thunk.org>

On Mon, Jan 30, 2017 at 05:42:38PM -0500, Theodore Ts'o wrote:
> On Mon, Jan 30, 2017 at 01:36:47PM -0800, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> > 
> > We can improve test coverage and simplify the test_dummy_encryption
> > kernel logic by requiring userspace to add a default master key to the
> > keyring.  Update xfstests-bld to do this.  This allows xfstests-bld to
> > test kernels with the corresponding kernel patch applied ("fscrypt: make
> > test_dummy_encryption require a keyring key").  It can still test older
> > kernels too; the key just doesn't get used in that case.
> > 
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> 
> This is upstream already.  (commit: ce7ef24b3ef1940)
> 
> 					- Ted

I don't see it.  Can you push out what you have, to both the kernel.org and
github repositories?

Eric

  reply	other threads:[~2017-01-30 23:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 21:36 [PATCH v2] xfstests-bld: populate keyring with default key for test_dummy_encryption Eric Biggers
2017-01-30 22:42 ` Theodore Ts'o
2017-01-30 23:03   ` Eric Biggers [this message]
2017-01-31  3:56     ` Theodore Ts'o

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=20170130230352.GA24293@gmail.com \
    --to=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=fstests@vger.kernel.org \
    --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