Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp858730ybz; Wed, 22 Apr 2020 09:11:38 -0700 (PDT) X-Google-Smtp-Source: APiQypL+42Mzkatp4jHUPNpgmQZSuoSvQXJmcYpc3wGByLYsV35uHqg5JfeWjWAlWTXyYkb9Rmei X-Received: by 2002:a50:ef09:: with SMTP id m9mr15190615eds.321.1587571897987; Wed, 22 Apr 2020 09:11:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587571897; cv=none; d=google.com; s=arc-20160816; b=Yr6yxwoVISgmjdZWSX92wuQ6RWzf0/oZYwwE2+sW4h9jQTOOwaCMVoRJcuvETTxS2f GbKspJ+LgUAW8xUoilEsWOuYOxOxwYILw4G5us3AGfOnheFjWdcSNJYvivnmGdih2uqw e5dE/XmTcCsYY+rwOS1cHbZRzNpRTbAzwpnZyRPrF3UyPzM5YsaxrjDHiGrvu4+pLyI1 6Ma3z0S5DkBHRMIY3vSgdROZZEwKH6C4jwyLlkqrt68KU56BzWeBjQ1AL7Qo4oDjrInV A7wS50rMlxS4/NorZYcn7TCF1kiPhgS+WWZ4WJrNggMiSS1DgQ0ZPv2W2XS9Vo7/ywP+ 61ng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=dtFTQ1NhCGGC/oKsZLumA4JYyATw+DaMw0xmBb9Udhg=; b=0QTsphvY1lXp6Q4IbSYhbY7lbuiLftYz54dnYX1Rt+Awy7oINEQ+nRwcXtYerlPqdD +efDm/07aUE/kaYlST39pDBjavG6VKYtsj4yiwopbw86/sN2ZR8ngYFyePKh+K3biPWM 3iIEoqSr/7F60M7gOdM2RqAEdlYYOPtFg6kP6HvjNEX7lKFRne/yApchgqUk4frPtrDP ZOpDGJLXZ4JXrwpCrYrHP3eA81fLsq5YWS5MPWzZq3+AdHpyJWN3RTR+VKk/3LSSNgO9 FF5lIYnqIDvtENsLqZAGS+BAiRCGbTxzrh33uyMNJKOEmYAaUAJX2Bo8JhVCiGDxvNhc mtFw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-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 pj7si3840046ejb.221.2020.04.22.09.10.32; Wed, 22 Apr 2020 09:11:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-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-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726421AbgDVQKc (ORCPT + 99 others); Wed, 22 Apr 2020 12:10:32 -0400 Received: from mx2.suse.de ([195.135.220.15]:36312 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726183AbgDVQKb (ORCPT ); Wed, 22 Apr 2020 12:10:31 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id A134AAED7; Wed, 22 Apr 2020 16:10:29 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id BA3291E0E56; Wed, 22 Apr 2020 18:10:29 +0200 (CEST) Date: Wed, 22 Apr 2020 18:10:29 +0200 From: Jan Kara To: Ira Weiny Cc: "Theodore Y. Ts'o" , Ext4 Developers List , syzkaller-bugs@googlegroups.com, stable@kernel.org, syzbot+bca9799bf129256190da@syzkaller.appspotmail.com Subject: Re: [PATCH] ext4: reject mount options not supported when remounting in handle_mount_opt() Message-ID: <20200422161029.GD20756@quack2.suse.cz> References: <20200415174839.461347-1-tytso@mit.edu> <20200415202537.GA2309605@iweiny-DESK2.sc.intel.com> <20200415220752.GA5187@mit.edu> <20200416052352.GK2309605@iweiny-DESK2.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200416052352.GK2309605@iweiny-DESK2.sc.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Wed 15-04-20 22:23:52, Ira Weiny wrote: > On Wed, Apr 15, 2020 at 06:07:52PM -0400, Theodore Y. Ts'o wrote: > > On Wed, Apr 15, 2020 at 01:25:37PM -0700, Ira Weiny wrote: > > > This fundamentally changes the behavior from forcing the dax mode to be the > > > same across the remount to only failing if we are going from non-dax to dax, > > > adding -o dax on the remount? > > > > > > But going from -o dax to 'not -o dax' would be ok? > > > > > > FWIW after thinking about it some I _think_ it would be ok to allow the dax > > > mode to change on a remount and let the inodes in memory stay in the mode they > > > are at. And newly loaded inodes would get the new mode... Unfortunately > > > without the STATX patch I have proposed the user does not have any way of > > > knowing which files are in which mode. > > > > We don't currently support mount -o nodax. > > But we do support not supplying the option which means 'nodax' right? Yeah, I second what Ira wrote. The new code does not seem to properly detect a case when enabled mount option is removed for remount and thus the feature would get disabled during remount as a result... Honza -- Jan Kara SUSE Labs, CR