From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: Eric Biggers <ebiggers@google.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, linux-mtd@lists.infradead.org,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2 00/15] fscrypt: improved logging and other cleanups
Date: Sun, 20 May 2018 20:55:48 -0400 [thread overview]
Message-ID: <20180521005548.GB4464@thunk.org> (raw)
In-Reply-To: <20180430225149.183514-1-ebiggers3@gmail.com>
On Mon, Apr 30, 2018 at 03:51:34PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Hello, here's yet another round of cleanups for fscrypt. Please
> consider for v4.18. These are all patches I've sent out previously.
> The series is based on v4.17-rc3.
>
> Patches 1-12 mostly remove unnecessary or redundant code from a number
> of different places; nothing particularly noteworthy. Note: to avoid a
> merge conflict with f2fs/dev, I've dropped the patch
> "fscrypt: remove WARN_ON_ONCE() when decryption fails".
>
> Patch 13 switches the existing warning and error messages in fscrypt
> over to use a common logging function, which is ratelimited and includes
> the filesystem name (->s_id) when available as well as a consistent
> prefix of "fscrypt:".
>
> Patches 14-15 are optimizations and cleanups for key lookup and key
> derivation. They are extracted from the patch "fscrypt: refactor
> finding and deriving key" I had originally sent as part of the series
> "fscrypt: filesystem-level keyring and v2 policy support". But I think
> they're useful changes by themselves, so no need to wait on them.
Thanks, I've applied this patch series.
- Ted
> Eric Biggers (15):
> fs, fscrypt: only define ->s_cop when FS_ENCRYPTION is enabled
> fscrypt: clean up after fscrypt_prepare_lookup() conversions
> fscrypt: remove unnecessary NULL check when allocating skcipher
> fscrypt: remove error messages for skcipher_request_alloc() failure
> fscrypt: remove stale comment from fscrypt_d_revalidate()
> fscrypt: don't clear flags on crypto transform
> fscrypt: don't special-case EOPNOTSUPP from
> fscrypt_get_encryption_info()
> fscrypt: drop max_namelen check from fname_decrypt()
> fscrypt: drop empty name check from fname_decrypt()
> fscrypt: make fscrypt_operations.max_namelen an integer
> fscrypt: remove unnecessary check for non-logon key type
> fscrypt: remove internal key size constants
> fscrypt: use a common logging function
> fscrypt: separate key lookup from key derivation
> fscrypt: only derive the needed portion of the key
>
> fs/crypto/crypto.c | 36 ++++--
> fs/crypto/fname.c | 32 ++---
> fs/crypto/fscrypt_private.h | 19 +--
> fs/crypto/hooks.c | 5 +-
> fs/crypto/keyinfo.c | 200 +++++++++++++++++---------------
> fs/ext4/super.c | 8 +-
> fs/f2fs/super.c | 8 +-
> fs/ubifs/crypto.c | 10 +-
> include/linux/fs.h | 4 +-
> include/linux/fscrypt_notsupp.h | 10 --
> include/linux/fscrypt_supp.h | 16 +--
> 11 files changed, 161 insertions(+), 187 deletions(-)
>
> --
> 2.17.0.441.gb46fe60e1d-goog
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2018-05-21 0:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 22:51 [PATCH v2 00/15] fscrypt: improved logging and other cleanups Eric Biggers
2018-04-30 22:51 ` [PATCH 01/15] fs, fscrypt: only define ->s_cop when FS_ENCRYPTION is enabled Eric Biggers
2018-04-30 22:51 ` [PATCH 02/15] fscrypt: clean up after fscrypt_prepare_lookup() conversions Eric Biggers
2018-04-30 22:51 ` [PATCH 03/15] fscrypt: remove unnecessary NULL check when allocating skcipher Eric Biggers
2018-04-30 22:51 ` [PATCH 04/15] fscrypt: remove error messages for skcipher_request_alloc() failure Eric Biggers
2018-04-30 22:51 ` [PATCH 05/15] fscrypt: remove stale comment from fscrypt_d_revalidate() Eric Biggers
2018-04-30 22:51 ` [PATCH 06/15] fscrypt: don't clear flags on crypto transform Eric Biggers
2018-04-30 22:51 ` [PATCH 07/15] fscrypt: don't special-case EOPNOTSUPP from fscrypt_get_encryption_info() Eric Biggers
2018-04-30 22:51 ` [PATCH 08/15] fscrypt: drop max_namelen check from fname_decrypt() Eric Biggers
2018-04-30 22:51 ` [PATCH 09/15] fscrypt: drop empty name " Eric Biggers
2018-04-30 22:51 ` [PATCH 10/15] fscrypt: make fscrypt_operations.max_namelen an integer Eric Biggers
2018-04-30 22:51 ` [PATCH 11/15] fscrypt: remove unnecessary check for non-logon key type Eric Biggers
2018-04-30 22:51 ` [PATCH 12/15] fscrypt: remove internal key size constants Eric Biggers
2018-04-30 22:51 ` [PATCH 13/15] fscrypt: use a common logging function Eric Biggers
2018-04-30 22:51 ` [PATCH 14/15] fscrypt: separate key lookup from key derivation Eric Biggers
2018-04-30 22:51 ` [PATCH 15/15] fscrypt: only derive the needed portion of the key Eric Biggers
2018-05-21 0:55 ` Theodore Y. Ts'o [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=20180521005548.GB4464@thunk.org \
--to=tytso@mit.edu \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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).