From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, tytso@mit.edu
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 6/8] fs crypto: add Makefile and Kconfig
Date: Mon, 15 Feb 2016 18:13:10 -0800 [thread overview]
Message-ID: <1455588792-87825-6-git-send-email-jaegeuk@kernel.org> (raw)
In-Reply-To: <1455588792-87825-1-git-send-email-jaegeuk@kernel.org>
This patch adds a facility to enable per-file encryption.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/Kconfig | 2 ++
fs/Makefile | 1 +
fs/crypto/Kconfig | 16 ++++++++++++++++
fs/crypto/Makefile | 2 ++
4 files changed, 21 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..fc5a4f9
--- /dev/null
+++ b/fs/crypto/Kconfig
@@ -0,0 +1,16 @@
+config FS_ENCRYPTION
+ bool "FS Encryption (Per-file encryption)"
+ 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
--
2.6.3
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
next prev parent reply other threads:[~2016-02-16 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 2:13 [PATCH 1/8] fs crypto: add basic definitions for per-file encryption Jaegeuk Kim
2016-02-16 2:13 ` [PATCH 2/8] fs crypto: add crypto.c for encrypt/decrypt functions Jaegeuk Kim
2016-02-16 2:13 ` [PATCH 3/8] fs crypto: add policy.c to handle contexts Jaegeuk Kim
2016-02-16 2:13 ` [PATCH 4/8] fs crypto: add keyinfo.c to handle permissions Jaegeuk Kim
2016-02-16 2:13 ` [PATCH 5/8] fs crypto: add fname.c to support filename encryption Jaegeuk Kim
2016-02-16 2:13 ` Jaegeuk Kim [this message]
2016-02-16 2:13 ` [PATCH 7/8] f2fs crypto: migrate into vfs's crypto engine Jaegeuk Kim
2016-02-16 2:13 ` [PATCH 8/8] ext4 " 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=1455588792-87825-6-git-send-email-jaegeuk@kernel.org \
--to=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).