From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0F45CC4338F for ; Tue, 24 Aug 2021 07:34:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EA875610D0 for ; Tue, 24 Aug 2021 07:34:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235073AbhHXHfI (ORCPT ); Tue, 24 Aug 2021 03:35:08 -0400 Received: from verein.lst.de ([213.95.11.211]:50571 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234817AbhHXHfE (ORCPT ); Tue, 24 Aug 2021 03:35:04 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 1B37B67373; Tue, 24 Aug 2021 09:34:19 +0200 (CEST) Date: Tue, 24 Aug 2021 09:34:18 +0200 From: Christoph Hellwig To: Gabriel Krisman Bertazi Cc: Christoph Hellwig , Shreeya Patel , linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [PATCH 05/11] unicode: pass a UNICODE_AGE() tripple to utf8_load Message-ID: <20210824073418.GA25209@lst.de> References: <20210818140651.17181-1-hch@lst.de> <20210818140651.17181-6-hch@lst.de> <87tujg19wj.fsf@collabora.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87tujg19wj.fsf@collabora.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Mon, Aug 23, 2021 at 11:02:52AM -0400, Gabriel Krisman Bertazi wrote: > I remember this fallback was specifically requested during a review or > in a discussion, but I honestly cannot remember the reason. > > One advantage I can think is if we have a filesystem that requires a > newer unicode version than the current kernel has, and strict mode flag > is set, we can fallback to the latest version and still mount the fs > read/write. Well, that seems a little pointless. If we add such a file system we can just upgrade the unÑ–code data files. (FYI, I did an upgrade to 1.13 to test this series, but without any file system that needs it I did not bother to submit the patch).