From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org
Subject: [PATCH 4/6] ext4.5: tweak the documentation for the encrypt feature
Date: Fri, 20 Sep 2019 14:29:52 -0700 [thread overview]
Message-ID: <20190920212954.205789-5-ebiggers@kernel.org> (raw)
In-Reply-To: <20190920212954.205789-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
Try to make it clearer that enabling 'encrypt' just enables *support*
for encryption; it doesn't actually encrypt anything by itself.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
misc/ext4.5.in | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/misc/ext4.5.in b/misc/ext4.5.in
index 627c0dad..1db61a5f 100644
--- a/misc/ext4.5.in
+++ b/misc/ext4.5.in
@@ -96,9 +96,9 @@ extended attributes per file.
.TP
.B encrypt
.br
-This ext4 feature provides file-system level encryption of data blocks
-and file names. The inode metadata (timestamps, file size, user/group
-ownership, etc.) is
+Enables support for file-system level encryption of data blocks and file
+names. The inode metadata (timestamps, file size, user/group ownership,
+etc.) is
.I not
encrypted.
.IP
--
2.23.0.351.gc4317032e6-goog
next prev parent reply other threads:[~2019-09-20 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 21:29 [PATCH 0/6] e2fsprogs: feature doc updates Eric Biggers
2019-09-20 21:29 ` [PATCH 1/6] ext4.5: move casefold feature to correct position Eric Biggers
2019-09-20 21:29 ` [PATCH 2/6] ext4.5: document first kernel version to support casefold feature Eric Biggers
2019-09-20 21:29 ` [PATCH 3/6] ext4.5: document the verity feature Eric Biggers
2019-09-20 21:29 ` Eric Biggers [this message]
2019-09-20 21:29 ` [PATCH 5/6] tune2fs.8: " Eric Biggers
2019-09-20 21:29 ` [PATCH 6/6] tune2fs.8: tweak the documentation for the encrypt feature 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=20190920212954.205789-5-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).