Skip to content

fscrypt: avoid ambiguous terms for "no-key name"

Eric Biggers linux-f2fs-devel linux-fscrypt linux-fsdevel 1 version Applied

Status from this message: Applied to fscrypt.git#master for 5.10.

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 1 replyApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/2fscrypt: don't call no-key names "ciphertext names"fs/crypto/fname.c fs/crypto/hooks.c fs/f2fs/dir.c +1 more+19 -200 replies
2/2fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAMEfs/crypto/fname.c fs/crypto/hooks.c include/linux/dcache.h +1 more+11 -120 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

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