[PATCH 5/5] fscrypt: remove mention of symlink st_size quirk from documentation
From: Eric Biggers <ebiggers@kernel.org>
Date: 2021-07-02 06:55:04
Also in:
linux-f2fs-devel, linux-fscrypt, linux-fsdevel
Subsystem:
documentation, fscrypt: file system level encryption support, the rest · Maintainers:
Jonathan Corbet, Eric Biggers, Theodore Y. Ts'o, Jaegeuk Kim, Linus Torvalds
From: Eric Biggers <redacted> Now that the correct st_size is reported for encrypted symlinks on all filesystems, update the documentation accordingly. Signed-off-by: Eric Biggers <redacted> --- Documentation/filesystems/fscrypt.rst | 5 ----- 1 file changed, 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
--
2.32.0