From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail.kernel.org ([198.145.29.99]:32938 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726678AbeHXVTO (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
        Fri, 24 Aug 2018 17:19:14 -0400
Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43])
        (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
        (No client certificate requested)
        by mail.kernel.org (Postfix) with ESMTPSA id A24D721557
        for <linux-fsdevel@vger.kernel.org>; Fri, 24 Aug 2018 17:43:35 +0000 (UTC)
Received: by mail-wm0-f43.google.com with SMTP id c14-v6so2304540wmb.4
        for <linux-fsdevel@vger.kernel.org>; Fri, 24 Aug 2018 10:43:35 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <15252.1535130642@warthog.procyon.org.uk>
References: <CAJfpegvh_NoXxwMEhrmUdt5C4djMy=gKLBHqe-79XUWOi0j9eQ@mail.gmail.com>
 <20180823223145.GK6515@ZenIV.linux.org.uk> <CALCETrVnwFGhZ0XWqyAsrOka43VohncrSd-gYgXXKxWHw+CmXg@mail.gmail.com>
 <24340.1535069316@warthog.procyon.org.uk> <CALCETrUOkkxYO__=ORad9XUJcW31ork6+kzo4-QHET5WSXfgYQ@mail.gmail.com>
 <20180824003105.GL6515@ZenIV.linux.org.uk> <184842E4-9368-463D-9131-D9A5F686C319@amacapital.net>
 <20180824031311.GM6515@ZenIV.linux.org.uk> <CALCETrVZKiQ=DJqnBiUEcMNypFjS=6PDmcjWoO0drbchs-KPzw@mail.gmail.com>
 <20180824060532.GG16817@thunk.org> <362.1535103931@warthog.procyon.org.uk>
 <015EF93F-1BC8-4000-ABBC-233F73D09384@amacapital.net> <CAJfpeguck9+a7qEe-1Q6HuCRDrfjNO-up8RK1C4gKSBWrwW=jg@mail.gmail.com>
 <F5276157-1D28-4B6F-AD08-55E3021434F0@amacapital.net> <15252.1535130642@warthog.procyon.org.uk>
From: Andy Lutomirski <luto@kernel.org>
Date: Fri, 24 Aug 2018 10:43:13 -0700
Message-ID: <CALCETrWZZfTcRn-0Gy0nbKv8vCUAKn+r032aFd-dSpZRdAU7aA@mail.gmail.com>
Subject: Re: [git pull] new mount API
To: David Howells <dhowells@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
        "Theodore Y. Ts'o" <tytso@mit.edu>,
        Al Viro <viro@zeniv.linux.org.uk>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Linux FS Devel <linux-fsdevel@vger.kernel.org>,
        Linux API <linux-api@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Fri, Aug 24, 2018 at 10:10 AM, David Howells <dhowells@redhat.com> wrote=
:
> Andy Lutomirski <luto@amacapital.net> 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=E2=80=99s rather unfriendly to users.
>
> The default behaviour has to be the same as mount(2).
>

Why?

Obviously mount(2) needs to keep working the way it does now.  Most
likely mount(8) also needs to retain its current behavior.  But I
don't see why the new API needs be bug-compatible with mount(2).

--Andy