linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Ferraris <arnaud.ferraris@collabora.com>
To: linux-ext4@vger.kernel.org
Cc: Daniel Rosenberg <drosen@google.com>,
	Gabriel Krisman Bertazi <krisman@collabora.com>,
	Arnaud Ferraris <arnaud.ferraris@collabora.com>
Subject: [PATCH v2 11/12] e2fsck.8.in: Document check_encoding extended option
Date: Fri, 27 Nov 2020 18:01:15 +0100	[thread overview]
Message-ID: <20201127170116.197901-12-arnaud.ferraris@collabora.com> (raw)
In-Reply-To: <20201127170116.197901-1-arnaud.ferraris@collabora.com>

From: Gabriel Krisman Bertazi <krisman@collabora.com>

Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
---
 e2fsck/e2fsck.8.in | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/e2fsck/e2fsck.8.in b/e2fsck/e2fsck.8.in
index 4e3890b2..019a34ec 100644
--- a/e2fsck/e2fsck.8.in
+++ b/e2fsck/e2fsck.8.in
@@ -267,6 +267,10 @@ Only fix damaged metadata; do not optimize htree directories or compress
 extent trees.  This option is incompatible with the -D and -E bmap2extent
 options.
 .TP
+.BI check_encoding
+Force verification of encoded filenames in case-insensitive directories.
+This is the default mode if the filesystem has the strict flag enabled.
+.TP
 .BI unshare_blocks
 If the filesystem has shared blocks, with the shared blocks read-only feature
 enabled, then this will unshare all shared blocks and unset the read-only
-- 
2.28.0


  parent reply	other threads:[~2020-11-27 17:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 17:01 [PATCH v2 00/12] e2fsprogs: improve case-insensitive fs support Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 01/12] tune2fs: Allow enabling casefold feature after fs creation Arnaud Ferraris
2020-12-07 17:17   ` Gabriel Krisman Bertazi
2020-11-27 17:01 ` [PATCH v2 02/12] tune2fs: Fix casefold+encrypt error message Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 03/12] ext2fs: Add method to validate casefolded strings Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 04/12] ext2fs: Implement faster CI comparison of strings Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 05/12] e2fsck: add new problem for casefolded name check Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 06/12] e2fsck: Fix entries with invalid encoded characters Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 07/12] e2fsck: Support casefold directories when rehashing Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 08/12] dict: Support comparison with context Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 09/12] e2fsck: Detect duplicated casefolded direntries for rehash Arnaud Ferraris
2020-11-27 17:01 ` [PATCH v2 10/12] e2fsck: Add option to force encoded filename verification Arnaud Ferraris
2020-11-27 17:01 ` Arnaud Ferraris [this message]
2020-11-27 17:01 ` [PATCH v2 12/12] tests: f_bad_fname: Test fixes of invalid filenames and duplicates Arnaud Ferraris

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=20201127170116.197901-12-arnaud.ferraris@collabora.com \
    --to=arnaud.ferraris@collabora.com \
    --cc=drosen@google.com \
    --cc=krisman@collabora.com \
    --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).