From: Dai Xiang <xiangx.dai@intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: How to enable CONFIG_EXT4_ENCRYPTION
Date: Tue, 8 Aug 2017 11:22:37 +0800 [thread overview]
Message-ID: <20170808032237.ukfjpgz32wn7x2zh@linux> (raw)
In-Reply-To: <20170807134942.u3ep5ivfq4ublueb@thunk.org>
On Mon, Aug 07, 2017 at 09:49:42AM -0400, Theodore Ts'o wrote:
> On Mon, Aug 07, 2017 at 05:51:26PM +0800, Dai Xiang wrote:
> > On Mon, Aug 07, 2017 at 11:25:02AM +0800, Dai Xiang wrote:
> > > Hi!
> > >
> > > I use xfstests with ext4 fs to test, and i found a skip:
> > >
> > > ext4/024 [not run] kernel does not support ext4 encryption
>
> Yeah, the message printed is misleading, and should be fixed.
> Checking to see whether the kernel supports encryption can be done by
> checking for the existence of the file:
>
> /sys/fs/ext4/features/encryption
>
> > i print the cmd:
> > /usr/sbin/xfs_io -i -c set_encpolicy /fs/scratch/tmpdir
> > /fs/scratch/tmpdir: failed to set encryption policy: Inappropriate
> > ioctl for device <===
> >
> > Seems do not related to kconfig?
>
> Yes, the issue is that you need to create the file system (or set via
> tune2fs) the feature flag "encrypt". To best test the read/write
> paths, you should set the mount option test_dummy_encryption. The
> kvm-xfstests and gce-xfstests framework do all of this automatically.
> From xfstests-bld/kvm-xfstests/test-appliance/files/root/cfg/fs/ext4/encrypt:
>
> SIZE=small
> export EXT_MKFS_OPTIONS="-O encrypt"
> export EXT_MOUNT_OPTIONS="test_dummy_encryption"
> REQUIRE_FEATURE=encryption
> TESTNAME="Ext4 encryption"
I just want to use mkfs and mount to enable this feature, could you
help give me an example about it?
Thanks
Xiang
>
> There are a number tests that are known to fail; primarily having to
> do with quota support, which doesn't play well with
> test_dummy_encryption (that's more of a test problem than anything
> else). See the encrypt.exclude file in that directory for more
> details.
>
> Cheers,
>
> - Ted
prev parent reply other threads:[~2017-08-08 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 3:25 How to enable CONFIG_EXT4_ENCRYPTION Dai Xiang
2017-08-07 9:51 ` Dai Xiang
2017-08-07 13:49 ` Theodore Ts'o
2017-08-07 19:31 ` Eric Biggers
2017-08-08 1:27 ` Dai Xiang
2017-08-08 5:50 ` Eric Biggers
2017-08-08 6:03 ` Dai Xiang
2017-08-08 13:19 ` Theodore Ts'o
2017-08-08 3:22 ` Dai Xiang [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=20170808032237.ukfjpgz32wn7x2zh@linux \
--to=xiangx.dai@intel.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).