Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp274115pxb; Mon, 16 Aug 2021 05:19:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw/qwpEIdSyvEJz9ekQnJyjiAcHvFa3iHKAlxJlyq842Hc/KtFRMNfVGRje0KY7Zt3vzYU+ X-Received: by 2002:a02:a709:: with SMTP id k9mr4586968jam.64.1629116343815; Mon, 16 Aug 2021 05:19:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629116343; cv=none; d=google.com; s=arc-20160816; b=Roh3xgszZ9BTKgsX6620ylDQrwB/CuDySTBsoxoTXqzenXJdg8YIVHxbnqG02PKrm/ 9Re1AJmb72ecBBlUYkWPlwvguZ58rqcc+0w3ftX1csIFcInFVINX/ADPUStz/WVC948+ cuTrpUxr9IiRiGAveyOgNn+fdUOOUaZ5YmvBMjc6CRC9edMpKt+ElFGhVTy25H+AZEV2 Wxe+tTs5hcPGxCmYOgTLNDwIPuYdmSN8jzgNH9YS+BNlhc5lyezE7f8TYJTobzo56wAB ZkJZ66MavcAcOTPT7fWnpBZ3fwthKLr5xAhPopIWKfwF2NPObbxh3QHlwWb4C7aJUnop Z9Ew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=iISnOy72ZoYt6kNjsxopgpzRRzcy3Dfuue/bnwhwsJY=; b=FfpwuDI2DFm2eqwtgr/JZSm1RnRStnnZyFKM3GF4ytkPE9aZubu0G6rzf1S+AUj2R1 vBPGKc3RIvHaZRv0OTfghCE9FqnlFnB5esrjZm3+UwRVhrl+ryopzt0gg9Nj3xjw/QRQ Kt2Tkoa/xe+e1nr0C89qlm+pL6STKVLHzjaZ2NVlkw2Z+GPZAKkbWTRU26ya8GIweM7z kRsJlN+bDDALs1UEpcsX1KpEpdOGL/Cn0x/9dXoo0mbUQOCoIsD49zLUh/MXEHOStviW ox2VV68PitQ4HyIjdb9+k4KqzDc/+tz2YIth3hhL9imalmlnXeBDrqO86v90erWxL8w4 A8kQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k39si10634257jav.114.2021.08.16.05.18.51; Mon, 16 Aug 2021 05:19:03 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233796AbhHPMS1 (ORCPT + 99 others); Mon, 16 Aug 2021 08:18:27 -0400 Received: from verein.lst.de ([213.95.11.211]:54190 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233062AbhHPMS0 (ORCPT ); Mon, 16 Aug 2021 08:18:26 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id B0EC36736F; Mon, 16 Aug 2021 14:17:52 +0200 (CEST) Date: Mon, 16 Aug 2021 14:17:52 +0200 From: Christoph Hellwig To: Kari Argillander Cc: Konstantin Komarov , Christoph Hellwig , ntfs3@lists.linux.dev, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Pali =?iso-8859-1?Q?Roh=E1r?= , Matthew Wilcox Subject: Re: [RFC PATCH 1/4] fs/ntfs3: Use new api for mounting Message-ID: <20210816121752.GA16815@lst.de> References: <20210816024703.107251-1-kari.argillander@gmail.com> <20210816024703.107251-2-kari.argillander@gmail.com> <20210816032351.yo7lkfrwsio3qvjw@kari-VirtualBox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210816032351.yo7lkfrwsio3qvjw@kari-VirtualBox> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 16, 2021 at 06:23:51AM +0300, Kari Argillander wrote: > > Nls loading is changed a little bit because new api not have default > > optioni for mount parameters. So we need to load nls table before and > > change that if user specifie someting else. > > > > Also try to use fsparam_flag_no as much as possible. This is just nice > > little touch and is not mandatory but it should not make any harm. It > > is just convenient that we can use example acl/noacl mount options. > > I would like that if someone can comment can we do reconfigure so that > we change mount options? Can we example change iocharset and be ok after > that? I have look some other fs drivers and in my eyes it seems to be > quite random if driver should let reconfigure all parameters. Right now > code is that we can reconfigure every mount parameter but I do not know > if this is right call. Reconfiguring non-trivial mount parameters is hard. In general I'd recommend to only allow reconfiguring paramters that a) have user demand for that b) you know what you're actually doing. Something like the iocharset clearly isn't something that makes sense to be changed.