[PATCH 0/2] fscrypt: avoid ambiguous terms for "no-key name"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: linux-fscrypt@xxxxxxxxxxxxxxx
- Subject: [PATCH 0/2] fscrypt: avoid ambiguous terms for "no-key name"
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Date: Wed, 23 Sep 2020 21:26:22 -0700
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
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[IETF Sipping]
[Info Cyrus]
[ALSA User]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite News]
[Deep Creek Hot Springs]
[Yosemite Campsites]
[ISDN Cause Codes]