Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp1077843pxb; Wed, 6 Oct 2021 23:43:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzMz2+okQE5y5BGTEv0NOYUYTj9zRe6rL40GPpK9BVsnpjr7RyVVku4QqiIHtD2MXSYgBIv X-Received: by 2002:a50:da0a:: with SMTP id z10mr3798407edj.298.1633589025026; Wed, 06 Oct 2021 23:43:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633589025; cv=none; d=google.com; s=arc-20160816; b=UCJCABQzb8xoeQUiJR8qsHeGX4OpqcEL5OtJzBu8Wo7WJj8SguduaXWt7eMUzYLdCF 4SOoCutOUBTZ3O3FpthRQQ3PULGh5RqnPhytmMKjm7xfjsZQt9WrdOcM/2LfR0WRVa7T iJYbir5myIO6ajfR9MNq9V7JvVn8GS1HJWGMkZtAVEVI+3eBU/dRjGeG4GBVIXSGdLon ydrzT9PV5pzkvjb8dX4YBG3xcRJxvT8I4YL1Me6VIVNXrJskAMASt5rHGDxlYUgxZ0iJ f3grqik8wuxVPexkE03kXIQuD0GnHvJ59gJteb4XyaBP5HiEExsnreTwTqXF3YDGVzAl L4VQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=k5hlaLFbVGg/as7e+spgIQh7YH3cqk7Q/SCpP6FrcYA=; b=Wo72w+RgM8qTm7FAWaeO3acW8JkKFA391XsTU/fE13TdameLIohwivfn9zadKoz0TD 3fvdM+Mukn4zCJ5JgmE66WfNg5r3WD1CnKXX5BVnNpevtms/P30cbayCh47ijvSPLK0l dxUP2PpUzFxrY4bD/CXmDVncf+zfp15siOEy79A2j6Bn69ZKwFdA/X8DVQ/YHTbjqatj ZhTWAOqjwQkq8ghbR2QmrDV2fdUbhH+14xtylqLfAC4yNGSlxw3CYCqavIilfGOVr/2i AdveOsUqbYJrI/x1XuwjeukmNS5Fo36HJRuQ1bilgYMKHodxcNPTv6M2BHiaO8TeVamI JIVA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lb9si16212713ejc.232.2021.10.06.23.43.20; Wed, 06 Oct 2021 23:43:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232667AbhJGGbO (ORCPT + 99 others); Thu, 7 Oct 2021 02:31:14 -0400 Received: from out4436.biz.mail.alibaba.com ([47.88.44.36]:17471 "EHLO out4436.biz.mail.alibaba.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232418AbhJGGbO (ORCPT ); Thu, 7 Oct 2021 02:31:14 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R171e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04357;MF=hsiangkao@linux.alibaba.com;NM=1;PH=DS;RN=9;SR=0;TI=SMTPD_---0UqoCT-J_1633588156; Received: from B-P7TQMD6M-0146.local(mailfrom:hsiangkao@linux.alibaba.com fp:SMTPD_---0UqoCT-J_1633588156) by smtp.aliyun-inc.com(127.0.0.1); Thu, 07 Oct 2021 14:29:19 +0800 Date: Thu, 7 Oct 2021 14:29:16 +0800 From: Gao Xiang To: Liu Bo Cc: linux-erofs@lists.ozlabs.org, Chao Yu , LKML , Peng Tao , Yan Song , Changwei Ge , Liu Jiang , Joseph Qi Subject: Re: [PATCH v3 1/2] erofs: decouple basic mount options from fs_context Message-ID: References: <20211006194453.130447-1-hsiangkao@linux.alibaba.com> <20211007061048.GA84859@rsjd01523.et2sqa> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20211007061048.GA84859@rsjd01523.et2sqa> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bo, On Thu, Oct 07, 2021 at 02:10:48PM +0800, Liu Bo wrote: > On Thu, Oct 07, 2021 at 03:44:52AM +0800, Gao Xiang wrote: > > Previously, EROFS mount options are all in the basic types, so > > erofs_fs_context can be directly copied with assignment. However, > > when the multiple device feature is introduced, it's hard to handle > > multiple device information like the other basic mount options. > > > > There is no need to allocate the whole sb info in advance, instead, > > let's separate the basic mount options from fs_context, thus > > multiple device information can be handled gracefully then. > > This is a bit confusing, IIRC, currently erofs does not allocate the whole > sb info in advance, does it? No, it doesn't. I just mentioned there are 2 ways to pass fs private contexts to fs_context: 1) allocate sbi in advance by using fc->s_fs_info; 2) allocate/pass a fs private fs_context by using fc->fs_private; erofs uses the second way.... Actually I'm fine with getting rid of such expression to avoid confusion for the next version... Thanks, Gao Xiang > > thanks, > liubo