Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <856b44ac-c85e-07a4-bb3a-f38829b34d0a@bacher09.org>
Date:   Thu, 7 Jul 2022 23:51:19 +0300
MIME-Version: 1.0
Content-Language: en-US
To:     Eric Biggers <ebiggers@kernel.org>
Cc:     tytso@mit.edu, linux-ext4@vger.kernel.org, krisman@collabora.com
References: <YscmTC3Mk9OXqOgL@gmail.com>
 <20220707190456.64972-1-slava@bacher09.org> <Ysc5HYPXUs6rW02S@gmail.com>
From:   Slava Bacherikov <slava@bacher09.org>
Subject: Re: [PATCH v2] tune2fs: allow disabling casefold feature
In-Reply-To: <Ysc5HYPXUs6rW02S@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


07.07.2022 22:50, Eric Biggers wrote:
> On Thu, Jul 07, 2022 at 10:04:56PM +0300, Slava Bacherikov wrote:

> Also, what are the semantics of disabling casefold, exactly?  Do the encoding
> and encoding flags fields in the superblock also get cleared?
> 
> - Eric

Sorry, I've totally missed that. It worked just fine on a kernel 
compiled without casefold, because kernel is ignoring encoding if there 
is no casefold flag. And dumpe2fs wasn't showing character encoding on 
fs that had no casefold feature.

Anyway, I've already updated patch.

--
Slava Bacherikov