diff options
| author | Eric Biggers <ebiggers@google.com> | 2023-12-05 16:21:27 -0800 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2023-12-09 12:38:16 -0800 |
| commit | 0fc24a6549f9b6efc538b67a098ab577b1f9a00e (patch) | |
| tree | 880b85f9784ad0a82dfa0e04a1817492a1252730 /fs/crypto | |
| parent | 33318c0e6ba64876050def6432f80387c89d0fe6 (diff) | |
fscrypt: update comment for do_remove_key()
Adjust a comment that was missed during commit 15baf55481de
("fscrypt: track master key presence separately from secret").
Link: https://lore.kernel.org/r/20231206002127.14790-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
Diffstat (limited to 'fs/crypto')
| -rw-r--r-- | fs/crypto/keyring.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/fs/crypto/keyring.c b/fs/crypto/keyring.c index f34a9b0b9e92..0edf0b58daa7 100644 --- a/fs/crypto/keyring.c +++ b/fs/crypto/keyring.c @@ -1002,9 +1002,9 @@ static int try_to_lock_encrypted_files(struct super_block *sb, * FS_IOC_REMOVE_ENCRYPTION_KEY_ALL_USERS (all_users=true) always removes the * key itself. * - * To "remove the key itself", first we wipe the actual master key secret, so - * that no more inodes can be unlocked with it. Then we try to evict all cached - * inodes that had been unlocked with the key. + * To "remove the key itself", first we transition the key to the "incompletely + * removed" state, so that no more inodes can be unlocked with it. Then we try + * to evict all cached inodes that had been unlocked with the key. * * If all inodes were evicted, then we unlink the fscrypt_master_key from the * keyring. Otherwise it remains in the keyring in the "incompletely removed" |