From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] xfstests-bld: format filesystem with '-O encrypt' in encrypt config
Date: Tue, 7 Feb 2017 12:40:45 -0500 [thread overview]
Message-ID: <20170207174045.lf6fb342rfnva3cp@thunk.org> (raw)
In-Reply-To: <20170206214237.8838-2-ebiggers3@gmail.com>
On Mon, Feb 06, 2017 at 01:42:34PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> We were relying on the kernel setting the 'encrypt' feature flag for us.
> We should just do it in userspace when formatting the filesystem. This
> will allow us to eventually remove the kernel-side hack to force-set the
> 'encrypt' flag in the superblock.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Thanks, applied.
- Ted
next prev parent reply other threads:[~2017-02-07 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 21:42 [PATCH] xfstests-bld: format filesystem with '-O encrypt' in encrypt config Eric Biggers
2017-02-07 17:40 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-13 6:59 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=20170207174045.lf6fb342rfnva3cp@thunk.org \
--to=tytso@mit.edu \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=fstests@vger.kernel.org \
/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