From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org
Subject: [PATCH 5/6] tune2fs.8: document the verity feature
Date: Fri, 20 Sep 2019 14:29:53 -0700 [thread overview]
Message-ID: <20190920212954.205789-6-ebiggers@kernel.org> (raw)
In-Reply-To: <20190920212954.205789-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
misc/tune2fs.8.in | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/misc/tune2fs.8.in b/misc/tune2fs.8.in
index b60db6ed..f7c7d42d 100644
--- a/misc/tune2fs.8.in
+++ b/misc/tune2fs.8.in
@@ -631,6 +631,11 @@ keep a high watermark for the unused inodes in a filesystem, to reduce
time. The first e2fsck run after enabling this feature will take the
full time, but subsequent e2fsck runs will take only a fraction of the
original time, depending on how full the file system is.
+.TP
+.B verity
+Enable support for verity protected files.
+.B Tune2fs
+currently only supports setting this filesystem feature.
.RE
.IP
After setting or clearing
--
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 ` [PATCH 4/6] ext4.5: tweak the documentation for the encrypt feature Eric Biggers
2019-09-20 21:29 ` Eric Biggers [this message]
2019-09-20 21:29 ` [PATCH 6/6] tune2fs.8: " 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-6-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 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.