From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 2887C932 for ; Mon, 18 Aug 2014 08:35:41 +0000 (UTC) Received: from mail-qa0-f46.google.com (mail-qa0-f46.google.com [209.85.216.46]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 09F671F950 for ; Mon, 18 Aug 2014 08:35:39 +0000 (UTC) Received: by mail-qa0-f46.google.com with SMTP id v10so4099391qac.33 for ; Mon, 18 Aug 2014 01:35:39 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <87lhqmxyxn.fsf@x220.int.ebiederm.org> <20140818040014.GA10623@mail.hallyn.com> Date: Mon, 18 Aug 2014 10:35:39 +0200 Message-ID: From: Miklos Szeredi To: Andy Lutomirski Content-Type: text/plain; charset=UTF-8 Cc: Al Viro , ksummit-discuss@lists.linuxfoundation.org, "Serge E. Hallyn" Subject: Re: [Ksummit-discuss] Mount API? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , FYR here's Al's summary of the subject, which I think is a good starting point: "Frankly, I wonder if we are trying to pack too much into one syscall - not just in terms of overloading it (that much is obvious), but in terms of trying to cram a sequence of syscalls into one. If we end up introducing new API(s) for mount(), it's probably worth considering something like this: * open a connection to fs type driver, get a descriptor * use normal IO syscalls (usually just write(2)) on that descriptor to tell fs type driver what do we want. If any kind of authentication is needed, that's the time for doing it * attach the thing identified by that descriptor to mountpoint" Thanks, Miklos