diff options
| author |  Eric Biggers <ebiggers@google.com>
| 2020-09-23 21:26:24 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com>
| 2020-09-23 21:29:49 -0700 |
| commit | 501e43fbea468fa93c1dff0ee744e69303ef5a43 (patch) | |
| tree | 02dd7b1b1aa3fa2cf1a3555b9acad39eddc4c764 /fs/crypto/fname.c | |
| parent | fscrypt: don't call no-key names "ciphertext names" (diff) | |
| download | linux-501e43fbea468fa93c1dff0ee744e69303ef5a43.tar.gz linux-501e43fbea468fa93c1dff0ee744e69303ef5a43.tar.bz2 linux-501e43fbea468fa93c1dff0ee744e69303ef5a43.zip | |
fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAME
Originally we used the term "encrypted name" or "ciphertext name" to
mean the encoded filename that is shown when an encrypted directory is
listed without its key. But these terms are ambiguous since they also
mean the filename stored on-disk. "Encrypted name" is especially
ambiguous since it could also be understood to mean "this filename is
encrypted on-disk", similar to "encrypted file".
So we've started calling these encoded names "no-key names" instead.
Therefore, rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAME to avoid
confusion about what this flag means.
Link: https://lore.kernel.org/r/20200924042624.98439-3-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
Diffstat (limited to 'fs/crypto/fname.c')
| -rw-r--r-- | fs/crypto/fname.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/crypto/fname.c b/fs/crypto/fname.c index 391acea4bc96..c65979452844 100644 --- a/fs/crypto/fname.c +++ b/fs/crypto/fname.c @@ -541,7 +541,7 @@ static int fscrypt_d_revalidate(struct dentry *dentry, unsigned int flags) * reverting to no-key names without evicting the directory's inode * -- which implies eviction of the dentries in the directory. */ - if (!(dentry->d_flags & DCACHE_ENCRYPTED_NAME)) + if (!(dentry->d_flags & DCACHE_NOKEY_NAME)) return 1; /* |