From: Eric Biggers <ebiggers3@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: tytso@mit.edu, Eric Biggers <ebiggers3@gmail.com>,
mhalcrow@google.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
linux-ext4@vger.kernel.org
Subject: [PATCH 00/13] fscrypto: cleanups and fixes
Date: Sun, 3 Apr 2016 00:21:51 -0500 [thread overview]
Message-ID: <1459660924-2960-1-git-send-email-ebiggers3@gmail.com> (raw)
This patchset includes various cleanups for the new filesystem encryption
code as well as some bug fixes for the FS_IOC_SET_ENCRYPTION_POLICY ioctl.
Eric Biggers (13):
fscrypto: remove unnecessary includes
fscrypto: rename some functions for clarity
fscrypto: rename functions to load and unload inode encryption info
fscrypto: return bool instead of int where appropriate
fscrypto: comment improvements and fixes
fscrypto: crypto_alloc_skcipher() always returns an ERR_PTR(), never
NULL
fscrypto: simplify building key descriptor string
fscrypto: use standard macros from kernel.h
fscrypto: make fname_encrypt() actually return length of ciphertext
fscrypto: restrict setting new policy to empty files and directories
only
fscrypto: restrict setting encryption policy to inode owner
fscrypto: require write access to mount to set encryption policy
fscrypto: improve error handling in fscrypt_set_policy()
fs/crypto/crypto.c | 25 +++++----
fs/crypto/fname.c | 72 ++++++++++++++++----------
fs/crypto/keyinfo.c | 47 ++++++++---------
fs/crypto/policy.c | 131 +++++++++++++++++++++++++++--------------------
fs/f2fs/dir.c | 4 +-
fs/f2fs/f2fs.h | 6 +--
fs/f2fs/file.c | 10 ++--
fs/f2fs/inode.c | 2 +-
fs/f2fs/namei.c | 10 ++--
fs/f2fs/super.c | 2 +-
include/linux/fscrypto.h | 81 +++++++++++++++++++++--------
11 files changed, 236 insertions(+), 154 deletions(-)
--
2.7.4
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers3@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
jaegeuk@kernel.org, tytso@mit.edu, mhalcrow@google.com,
Eric Biggers <ebiggers3@gmail.com>
Subject: [PATCH 00/13] fscrypto: cleanups and fixes
Date: Sun, 3 Apr 2016 00:21:51 -0500 [thread overview]
Message-ID: <1459660924-2960-1-git-send-email-ebiggers3@gmail.com> (raw)
This patchset includes various cleanups for the new filesystem encryption
code as well as some bug fixes for the FS_IOC_SET_ENCRYPTION_POLICY ioctl.
Eric Biggers (13):
fscrypto: remove unnecessary includes
fscrypto: rename some functions for clarity
fscrypto: rename functions to load and unload inode encryption info
fscrypto: return bool instead of int where appropriate
fscrypto: comment improvements and fixes
fscrypto: crypto_alloc_skcipher() always returns an ERR_PTR(), never
NULL
fscrypto: simplify building key descriptor string
fscrypto: use standard macros from kernel.h
fscrypto: make fname_encrypt() actually return length of ciphertext
fscrypto: restrict setting new policy to empty files and directories
only
fscrypto: restrict setting encryption policy to inode owner
fscrypto: require write access to mount to set encryption policy
fscrypto: improve error handling in fscrypt_set_policy()
fs/crypto/crypto.c | 25 +++++----
fs/crypto/fname.c | 72 ++++++++++++++++----------
fs/crypto/keyinfo.c | 47 ++++++++---------
fs/crypto/policy.c | 131 +++++++++++++++++++++++++++--------------------
fs/f2fs/dir.c | 4 +-
fs/f2fs/f2fs.h | 6 +--
fs/f2fs/file.c | 10 ++--
fs/f2fs/inode.c | 2 +-
fs/f2fs/namei.c | 10 ++--
fs/f2fs/super.c | 2 +-
include/linux/fscrypto.h | 81 +++++++++++++++++++++--------
11 files changed, 236 insertions(+), 154 deletions(-)
--
2.7.4
next reply other threads:[~2016-04-03 5:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 5:21 Eric Biggers [this message]
2016-04-03 5:21 ` [PATCH 00/13] fscrypto: cleanups and fixes Eric Biggers
2016-04-03 5:21 ` [PATCH 01/13] fscrypto: remove unnecessary includes Eric Biggers
2016-04-03 5:21 ` Eric Biggers
2016-04-03 5:21 ` [PATCH 02/13] fscrypto: rename some functions for clarity Eric Biggers
2016-04-03 5:21 ` Eric Biggers
2016-04-03 7:45 ` Theodore Ts'o
2016-04-03 7:45 ` Theodore Ts'o
2016-04-03 5:21 ` [PATCH 03/13] fscrypto: rename functions to load and unload inode encryption info Eric Biggers
2016-04-03 5:21 ` Eric Biggers
2016-04-03 5:21 ` [PATCH 04/13] fscrypto: return bool instead of int where appropriate Eric Biggers
2016-04-03 5:21 ` Eric Biggers
2016-04-03 5:21 ` [PATCH 05/13] fscrypto: comment improvements and fixes Eric Biggers
2016-04-03 5:21 ` Eric Biggers
2016-04-03 5:21 ` [PATCH 06/13] fscrypto: crypto_alloc_skcipher() always returns an ERR_PTR(), never NULL Eric Biggers
2016-04-03 5:21 ` Eric Biggers
2016-04-03 5:21 ` [PATCH 07/13] fscrypto: simplify building key descriptor string Eric Biggers
2016-04-03 5:21 ` Eric Biggers
2016-04-03 5:21 ` [PATCH 08/13] fscrypto: use standard macros from kernel.h Eric Biggers
2016-04-03 5:21 ` Eric Biggers
2016-04-03 5:22 ` [PATCH 09/13] fscrypto: make fname_encrypt() actually return length of ciphertext Eric Biggers
2016-04-03 5:22 ` Eric Biggers
2016-04-03 5:22 ` [PATCH 10/13] fscrypto: restrict setting new policy to empty files and directories only Eric Biggers
2016-04-03 5:22 ` Eric Biggers
2016-04-03 5:22 ` [PATCH 11/13] fscrypto: restrict setting encryption policy to inode owner Eric Biggers
2016-04-03 5:22 ` Eric Biggers
2016-04-03 5:22 ` [PATCH 12/13] fscrypto: require write access to mount to set encryption policy Eric Biggers
2016-04-03 5:22 ` Eric Biggers
2016-04-03 5:22 ` [PATCH 13/13] fscrypto: improve error handling in fscrypt_set_policy() Eric Biggers
2016-04-03 5:22 ` 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=1459660924-2960-1-git-send-email-ebiggers3@gmail.com \
--to=ebiggers3@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.