[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y1z0vsoe.fsf@collabora.com>
Date: Tue, 17 May 2022 15:57:05 -0400
From: Gabriel Krisman Bertazi <krisman@...labora.com>
To: "Theodore Ts'o" <tytso@....edu>
Cc: adilger.kernel@...ger.ca, jaegeuk@...nel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
ebiggers@...nel.org, kernel@...labora.com
Subject: Re: [PATCH v4 00/10] Clean up the case-insensitive lookup path
"Theodore Ts'o" <tytso@....edu> writes:
> On Wed, May 11, 2022 at 03:31:36PM -0400, Gabriel Krisman Bertazi wrote:
>> The case-insensitive implementations in f2fs and ext4 have quite a bit
>> of duplicated code. This series simplifies the ext4 version, with the
>> goal of extracting ext4_ci_compare into a helper library that can be
>> used by both filesystems. It also reduces the clutter from many
>> codeguards for CONFIG_UNICODE; as requested by Linus, they are part of
>> the codeflow now.
>>
>> While there, I noticed we can leverage the utf8 functions to detect
>> encoded names that are corrupted in the filesystem. Therefore, it also
>> adds an ext4 error on that scenario, to mark the filesystem as
>> corrupted.
>
> Gabriel, are you planning on doing another version of this patch
> series?
> It looks like the first two patches for ext4 are not controversial, so
> I could take those, while some of the other patches have questions
> which Eric has raised.
Hi Ted,
I'll be reworking the series to apply Eric's comments and I might render
patch 1 unnecessary. I'd be happy to send a v5 for the whole thing
instead of applying the first two now.
Thanks,
--
Gabriel Krisman Bertazi
Powered by blists - more mailing lists