All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 5/5] fscrypt: remove mention of symlink st_size quirk from documentation
Date: Thu,  1 Jul 2021 23:53:50 -0700	[thread overview]
Message-ID: <20210702065350.209646-6-ebiggers@kernel.org> (raw)
In-Reply-To: <20210702065350.209646-1-ebiggers@kernel.org>

From: Eric Biggers <ebiggers@google.com>

Now that the correct st_size is reported for encrypted symlinks on all
filesystems, update the documentation accordingly.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 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


WARNING: multiple messages have this Message-ID

From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-mtd@lists.infradead.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 5/5] fscrypt: remove mention of symlink st_size quirk from documentation
Date: Thu,  1 Jul 2021 23:53:50 -0700	[thread overview]
Message-ID: <20210702065350.209646-6-ebiggers@kernel.org> (raw)
In-Reply-To: <20210702065350.209646-1-ebiggers@kernel.org>

From: Eric Biggers <ebiggers@google.com>

Now that the correct st_size is reported for encrypted symlinks on all
filesystems, update the documentation accordingly.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 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



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID

From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 5/5] fscrypt: remove mention of symlink st_size quirk from documentation
Date: Thu,  1 Jul 2021 23:53:50 -0700	[thread overview]
Message-ID: <20210702065350.209646-6-ebiggers@kernel.org> (raw)
In-Reply-To: <20210702065350.209646-1-ebiggers@kernel.org>

From: Eric Biggers <ebiggers@google.com>

Now that the correct st_size is reported for encrypted symlinks on all
filesystems, update the documentation accordingly.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 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


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2021-07-02  6:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  6:53 [PATCH 0/5] fscrypt: report correct st_size for encrypted symlinks Eric Biggers
2021-07-02  6:53 ` Eric Biggers
2021-07-02  6:53 ` [f2fs-dev] " Eric Biggers
2021-07-02  6:53 ` [PATCH 1/5] fscrypt: add fscrypt_symlink_getattr() for computing st_size Eric Biggers
2021-07-02  6:53   ` Eric Biggers
2021-07-02  6:53   ` [f2fs-dev] " Eric Biggers
2021-07-02  6:53 ` [PATCH 2/5] ext4: report correct st_size for encrypted symlinks Eric Biggers
2021-07-02  6:53   ` Eric Biggers
2021-07-02  6:53   ` [f2fs-dev] " Eric Biggers
2021-07-02  6:53 ` [PATCH 3/5] f2fs: " Eric Biggers
2021-07-02  6:53   ` Eric Biggers
2021-07-02  6:53   ` [f2fs-dev] " Eric Biggers
2021-07-02  6:53 ` [PATCH 4/5] ubifs: " Eric Biggers
2021-07-02  6:53   ` Eric Biggers
2021-07-02  6:53   ` [f2fs-dev] " Eric Biggers
2021-07-02  6:53 ` Eric Biggers [this message]
2021-07-02  6:53   ` [PATCH 5/5] fscrypt: remove mention of symlink st_size quirk from documentation Eric Biggers
2021-07-02  6:53   ` [f2fs-dev] " Eric Biggers
2021-07-26  3:58 ` [PATCH 0/5] fscrypt: report correct st_size for encrypted symlinks Eric Biggers
2021-07-26  3:58   ` Eric Biggers
2021-07-26  3:58   ` [f2fs-dev] " Eric Biggers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210702065350.209646-6-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.