From: Randy Dunlap <rdunlap@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, tytso@mit.edu,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 06/10] fs crypto: add Makefile and Kconfig
Date: Tue, 1 Mar 2016 10:30:42 -0800 [thread overview]
Message-ID: <56D5DFD2.9020008@infradead.org> (raw)
In-Reply-To: <20160301020447.GB60850@jaegeuk.hsd1.ca.comcast.net>
On 02/29/16 18:04, Jaegeuk Kim wrote:
> On Sun, Feb 28, 2016 at 09:39:39PM -0800, Randy Dunlap wrote:
>> On 02/25/16 11:26, Jaegeuk Kim wrote:
>>> This patch adds a facility to enable per-file encryption.
>>>
>>> Arnd fixes a missing CONFIG_BLOCK check in the original patch.
>>> "The newly added generic crypto abstraction for file systems operates
>>> on 'struct bio' objects, which do not exist when CONFIG_BLOCK is
>>> disabled:
>>>
>>> fs/crypto/crypto.c: In function 'fscrypt_zeroout_range':
>>> fs/crypto/crypto.c:308:9: error: implicit declaration of function 'bio_alloc' [-Werror=implicit-function-declaration]
>>>
>>> This adds a Kconfig dependency that prevents FS_ENCRYPTION from being
>>> enabled without BLOCK."
>>>
>>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>>> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>>> ---
>>> fs/Kconfig | 2 ++
>>> fs/Makefile | 1 +
>>> fs/crypto/Kconfig | 17 +++++++++++++++++
>>> fs/crypto/Makefile | 2 ++
>>> 4 files changed, 22 insertions(+)
>>> create mode 100644 fs/crypto/Kconfig
>>> create mode 100644 fs/crypto/Makefile
>>>
>>> diff --git a/fs/Kconfig b/fs/Kconfig
>>> index 9adee0d..9d75767 100644
>>> --- a/fs/Kconfig
>>> +++ b/fs/Kconfig
>>> @@ -84,6 +84,8 @@ config MANDATORY_FILE_LOCKING
>>>
>>> To the best of my knowledge this is dead code that no one cares about.
>>>
>>> +source "fs/crypto/Kconfig"
>>> +
>>> source "fs/notify/Kconfig"
>>>
>>> source "fs/quota/Kconfig"
>>> diff --git a/fs/Makefile b/fs/Makefile
>>> index 79f5225..47571e2 100644
>>> --- a/fs/Makefile
>>> +++ b/fs/Makefile
>>> @@ -30,6 +30,7 @@ obj-$(CONFIG_EVENTFD) += eventfd.o
>>> obj-$(CONFIG_USERFAULTFD) += userfaultfd.o
>>> obj-$(CONFIG_AIO) += aio.o
>>> obj-$(CONFIG_FS_DAX) += dax.o
>>> +obj-y += crypto/
>>> obj-$(CONFIG_FILE_LOCKING) += locks.o
>>> obj-$(CONFIG_COMPAT) += compat.o compat_ioctl.o
>>> obj-$(CONFIG_BINFMT_AOUT) += binfmt_aout.o
>>> diff --git a/fs/crypto/Kconfig b/fs/crypto/Kconfig
>>> new file mode 100644
>>> index 0000000..9bea124e
>>> --- /dev/null
>>> +++ b/fs/crypto/Kconfig
>>> @@ -0,0 +1,17 @@
>>> +config FS_ENCRYPTION
>>> + bool "FS Encryption (Per-file encryption)"
>>> + depends on BLOCK
>>
>> depends on CRYPTO
>
> This complains recursive dependency limitations, and I checked out that below
> ENCRYPTED_KEYS in security/keys/Kconfig selects CRYPTO.
I guess that this one also needs to select CRYPTO then.
> Thanks,
>
>> since all of the CRYPTO_xxx below also depend on CRYPTO.
>>
>>> + select CRYPTO_AES
>>> + select CRYPTO_CBC
>>> + select CRYPTO_ECB
>>> + select CRYPTO_XTS
>>> + select CRYPTO_CTS
>>> + select CRYPTO_CTR
>>> + select CRYPTO_SHA256
>>> + select KEYS
>>> + select ENCRYPTED_KEYS
>>> + help
>>> + Enable encryption of files and directories. This
>>> + feature is similar to ecryptfs, but it is more memory
>>> + efficient since it avoids caching the encrypted and
>>> + decrypted pages in the page cache.
>>> diff --git a/fs/crypto/Makefile b/fs/crypto/Makefile
>>> new file mode 100644
>>> index 0000000..f9f68cd
>>> --- /dev/null
>>> +++ b/fs/crypto/Makefile
>>> @@ -0,0 +1,2 @@
>>> +obj-y += fname.o
>>> +obj-$(CONFIG_FS_ENCRYPTION) += crypto.o policy.o keyinfo.o
>>>
>>
>>
>> --
>> ~Randy
--
~Randy
next prev parent reply other threads:[~2016-03-01 18:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 19:25 [PATCH 00/10 v2] File-level Encryption Support by VFS Jaegeuk Kim
2016-02-25 19:25 ` [PATCH 01/10] fs crypto: add basic definitions for per-file encryption Jaegeuk Kim
2016-02-29 5:41 ` Randy Dunlap
2016-03-01 1:35 ` Jaegeuk Kim
2016-03-11 5:00 ` Dan Williams
2016-03-11 18:50 ` Jaegeuk Kim
2016-02-25 19:26 ` [PATCH 02/10] fs crypto: add crypto.c for encrypt/decrypt functions Jaegeuk Kim
2016-02-25 19:26 ` [PATCH 03/10] fs crypto: add policy.c to handle contexts Jaegeuk Kim
2016-02-25 19:26 ` [PATCH 04/10] fs crypto: add keyinfo.c to handle permissions Jaegeuk Kim
2016-02-25 19:26 ` [PATCH 05/10] fs crypto: add fname.c to support filename encryption Jaegeuk Kim
2016-02-25 19:26 ` [PATCH 06/10] fs crypto: add Makefile and Kconfig Jaegeuk Kim
2016-02-29 5:39 ` Randy Dunlap
2016-03-01 2:04 ` Jaegeuk Kim
2016-03-01 18:30 ` Randy Dunlap [this message]
2016-02-25 19:26 ` [PATCH 07/10] fs crypto: add dentry revalidation facility in crypto Jaegeuk Kim
2016-02-25 19:26 ` [PATCH 08/10] f2fs crypto: migrate into vfs's crypto engine Jaegeuk Kim
2016-02-25 19:26 ` [PATCH 09/10] f2fs crypto: sync ext4_lookup and ext4_file_open Jaegeuk Kim
2016-02-25 19:26 ` [PATCH 10/10] ext4 crypto: migrate into vfs's crypto engine Jaegeuk Kim
-- strict thread matches above, loose matches on Subject: below --
2016-03-02 18:31 [PATCH v3 00/10] File-level Encryption Support by VFS Jaegeuk Kim
2016-03-02 18:31 ` [PATCH 06/10] fs crypto: add Makefile and Kconfig Jaegeuk Kim
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=56D5DFD2.9020008@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).