Return-Path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:56734 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726287AbeHXUqR (ORCPT ); Fri, 24 Aug 2018 16:46:17 -0400 From: David Howells In-Reply-To: References: <20180823223145.GK6515@ZenIV.linux.org.uk> <24340.1535069316@warthog.procyon.org.uk> <20180824003105.GL6515@ZenIV.linux.org.uk> <184842E4-9368-463D-9131-D9A5F686C319@amacapital.net> <20180824031311.GM6515@ZenIV.linux.org.uk> <20180824060532.GG16817@thunk.org> <362.1535103931@warthog.procyon.org.uk> <015EF93F-1BC8-4000-ABBC-233F73D09384@amacapital.net> To: Andy Lutomirski Cc: dhowells@redhat.com, Miklos Szeredi , "Theodore Y. Ts'o" , Al Viro , Linus Torvalds , Linux FS Devel , Linux API Subject: Re: [git pull] new mount API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Date: Fri, 24 Aug 2018 18:10:42 +0100 Message-ID: <15252.1535130642@warthog.procyon.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Andy Lutomirski wrote: > Hmm. Is it that case in the current patchset that you can do CMD_CREATE and > reconfigure the result and some *other* existing mount will change? If so, > that’s rather unfriendly to users. The default behaviour has to be the same as mount(2). David