Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp3000757ybi; Thu, 18 Jul 2019 19:02:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqzFNjFWrDcj75ANTDN78IfuOVTZwyNzSlRp7D7A9OW3GPs1TMXc1sGCI03JJzGO9Abh+Wj0 X-Received: by 2002:a17:90a:c68c:: with SMTP id n12mr54800536pjt.33.1563501727453; Thu, 18 Jul 2019 19:02:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563501727; cv=none; d=google.com; s=arc-20160816; b=zzdLpq1+O27mxHMU4is3Cxn8WG8jBdOJv5lA8P6rScIhm2v58r/Z9vfd1jm9LgvHo7 bUIQ67nyerepLYVFjkC2oej/rKUOZ02adfDP6ZFo4scQbfBv4PbenyTZlnMsX3lqhcSH 2n0CvNM9mUs4q7mRetcyyZLuFvtTm0bvtCJTSZ6X1BRX+so5E7xLpWqnypqLDfTfN5Ry +vsNn4880Gem4EAAKUnJNiFzcf4XG2bJPR3gkM9pxmZRlBlDOVzfQkAgDAissAPgTRXm 24bBR5gK1ELm0tUZn789t28BXq9sbIhxdpd+93YKuqphBaCLCgSS9sAaI1r/LB5bF2Q1 GOPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=TssCGOlneL6blW5L2MkGUuI1FojzwLzT66ZAavmYXNg=; b=NKcQ4L+VrwFZYjli6Fk2YyjoAj/qOdlT79Gm4dYw6fCC3TUugZ/gDNLepC6I0yBpmp hVZcU1RWU7KIXa86LrHDITvRQs/oSy+mGEfMbcC1t+nNZDqfWfJRloEd+DgKE0Htweom T4Ui5PwcK5HjgBtnsbya/uev6opdvUmJreX7kATDH3cAlPZn9Sm9/ZHE4HAJz6kzJvgb XJvk7ScVNvlCRkHqtchttkCo4P7O/wV4WNPFu5hzsYxHkkPPsGOjCDwGqxq4R+WQAfuN EKJm/PVDFOCRl8+HYcG2gYXasC8KSDdx4iLTkomXsjc0GBhyEi5qSJaG+OdVTDoBmdgf uEyA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r8si126947pgr.243.2019.07.18.19.01.51; Thu, 18 Jul 2019 19:02:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726431AbfGSCBd (ORCPT + 99 others); Thu, 18 Jul 2019 22:01:33 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:2681 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726042AbfGSCBd (ORCPT ); Thu, 18 Jul 2019 22:01:33 -0400 Received: from DGGEMS407-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id EEFA8E4162363BA56F5F; Fri, 19 Jul 2019 10:01:30 +0800 (CST) Received: from [10.134.22.195] (10.134.22.195) by smtp.huawei.com (10.3.19.207) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 19 Jul 2019 10:01:26 +0800 Subject: Re: [PATCH v2 2/2] f2fs: Support case-insensitive file name lookups To: Daniel Rosenberg , Jaegeuk Kim , Jonathan Corbet , CC: , , , References: <20190717031408.114104-1-drosen@google.com> <20190717031408.114104-3-drosen@google.com> <4ef17922-d1e9-1b83-9e89-d332ea6fb7ae@google.com> From: Chao Yu Message-ID: <8f1c8f28-9afa-94b0-05b2-12df71db201c@huawei.com> Date: Fri, 19 Jul 2019 10:01:25 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <4ef17922-d1e9-1b83-9e89-d332ea6fb7ae@google.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.134.22.195] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/7/19 5:31, Daniel Rosenberg wrote: > > On 7/17/19 3:11 AM, Chao Yu wrote: >> We need to add one more entry f2fs_fsflags_map[] to map F2FS_CASEFOLD_FL to >> FS_CASEFOLD_FL correctly and adapt F2FS_GETTABLE_FS_FL/F2FS_SETTABLE_FS_FL as well. > > I don't see FS_CASEFOLD_FL. It would make sense for it to exist, but unless it's in some recent patch I don't think that's currently in the kernel. Or are you suggesting adding it in this patch? Yeah, I think we can use a separated patch to propose uplifting the flag to a common one in fs.h, and then adjust f2fs_fsflags_map/F2FS_GETTABLE_FS_FL/F2FS_SETTABLE_FS_FL mapping. Otherwise we will fail to set CASEFOLD flag to inode. Thanks, > > . >