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

Eric Biggers
2020-09-24T04:29:02Z

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(-)

--
2.28.0