fscrypt: avoid ambiguous terms for "no-key name"
Status from this message: Applied to fscrypt.git#master for 5.10.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | fscrypt: don't call no-key names "ciphertext names"fs/ fs/ fs/ +1 more | +19 | 0 replies | |
| 2/2 | fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAMEfs/ fs/ include/ +1 more | +11 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] fscrypt: avoid ambiguous terms for "no-key name"
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(-)
Signature · 1 line
2.28.0