Re: [PATCH 0/2] fscrypt: avoid ambiguous terms for "no-key name"

Eric Biggers
2020-09-28T23:30:32Z

On Wed, Sep 23, 2020 at 09:26:22PM -0700, Eric Biggers wrote:
> This series fixes overloading of the terms "ciphertext name" and
> "encrypted name" to also sometimes mean "no-key name".
> The overloading of these terms has caused some confusion.
>
> No change in behavior.
>
> Eric Biggers (2):
> fscrypt: don't call no-key names "ciphertext names"
> fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAME
>
> fs/crypto/fname.c | 16 ++++++++--------
> fs/crypto/hooks.c | 13 ++++++-------
> fs/f2fs/dir.c | 2 +-
> include/linux/dcache.h | 2 +-
> include/linux/fscrypt.h | 25 ++++++++++++-------------
> 5 files changed, 28 insertions(+), 30 deletions(-)

Applied to fscrypt.git#master for 5.10.

- Eric