public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Dai Xiang <xiangx.dai@intel.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: How to enable CONFIG_EXT4_ENCRYPTION
Date: Tue, 8 Aug 2017 14:03:20 +0800	[thread overview]
Message-ID: <20170808060320.sh4pe4abekxhkonh@linux> (raw)
In-Reply-To: <20170808055013.GA593@zzz.localdomain>

On Mon, Aug 07, 2017 at 10:50:13PM -0700, Eric Biggers wrote:
> On Tue, Aug 08, 2017 at 09:27:38AM +0800, Dai Xiang wrote:
> > > 
> > > Actually, this is one of the tests in the "encrypt" group, which format the
> > > scratch device with "-O encrypt".  So I believe the printed message is correct.
> > > Are you 100% sure that CONFIG_EXT4_ENCRYPTION is enabled in your kernel config
> > > and that you are running the correct kernel?
> > 
> > I use v4.13-rc3 kernerl, and i find this info refer to https://wiki.archlinux.org/index.php/ext4#Using_file-based_encryption:
> > 
> > Ext4 forbids encrypting the root (/) directory and will produce an error on kernel 4.13 and later
> > 
> > Does it impact?
> > 
> 
> No, the tests do not try to encrypt the root directory.  Can you please double
> check that the kernel you're testing actually has CONFIG_EXT4_ENCRYPTION
> enabled?

oh, I see, i miss them, but i have a new question:

I have set CONFIG_FS_ENCRYPTION and CONFIG_EXT4_ENCRYPTION both y, but
after build the config do not include them, and what make me confused
is that there is no failure log about them.

Did i miss some dependence kconfigs or conflict kconfigs?

> 
> Eric

  reply	other threads:[~2017-08-08  6:04 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 [this message]
2017-08-08 13:19             ` Theodore Ts'o
2017-08-08  3:22     ` Dai Xiang

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=20170808060320.sh4pe4abekxhkonh@linux \
    --to=xiangx.dai@intel.com \
    --cc=ebiggers3@gmail.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