diff options
author | Eric Biggers <ebiggers@google.com> | 2021-07-01 23:53:50 -0700 |
---|---|---|
committer | Eric Biggers <ebiggers@google.com> | 2021-07-25 20:01:07 -0700 |
commit | e538b0985a05cfe245ada0bb92f177efec6b8a88 (patch) | |
tree | edcd3cc62371d220fd6abc83a1794d9aa463a4c7 | |
parent | 064c734986011390b4d111f1a99372b7f26c3850 (diff) | |
download | linux-e538b0985a05cfe245ada0bb92f177efec6b8a88.tar.bz2 |
fscrypt: remove mention of symlink st_size quirk from documentation
Now that the correct st_size is reported for encrypted symlinks on all
filesystems, update the documentation accordingly.
Link: https://lore.kernel.org/r/20210702065350.209646-6-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
-rw-r--r-- | Documentation/filesystems/fscrypt.rst | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/Documentation/filesystems/fscrypt.rst b/Documentation/filesystems/fscrypt.rst index 44b67ebd6e40..02ec57818920 100644 --- a/Documentation/filesystems/fscrypt.rst +++ b/Documentation/filesystems/fscrypt.rst @@ -1063,11 +1063,6 @@ astute users may notice some differences in behavior: - DAX (Direct Access) is not supported on encrypted files. -- The st_size of an encrypted symlink will not necessarily give the - length of the symlink target as required by POSIX. It will actually - give the length of the ciphertext, which will be slightly longer - than the plaintext due to NUL-padding and an extra 2-byte overhead. - - The maximum length of an encrypted symlink is 2 bytes shorter than the maximum length of an unencrypted symlink. For example, on an EXT4 filesystem with a 4K block size, unencrypted symlinks can be up |