From: Miklos Szeredi <miklos@szeredi.hu>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
ksummit-discuss@lists.linuxfoundation.org,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [Ksummit-discuss] Mount API?
Date: Mon, 18 Aug 2014 10:35:39 +0200 [thread overview]
Message-ID: <CAJfpegsoEGG2H1pFdBLAaosJhE8qbR69C9yikQHTd_egE001DA@mail.gmail.com> (raw)
In-Reply-To: <CALCETrW53hiZpFH4J+UsE_tX6i_cTmfth5xHtOzw8uPGGEbf4Q@mail.gmail.com>
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
next prev parent reply other threads:[~2014-08-18 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 3:24 Eric W. Biederman
2014-08-18 4:00 ` Serge E. Hallyn
2014-08-18 4:03 ` Andy Lutomirski
2014-08-18 8:35 ` Miklos Szeredi [this message]
2014-08-18 12:24 ` Theodore Ts'o
2014-08-19 2:06 ` Serge E. Hallyn
2014-08-19 2:49 ` Theodore Ts'o
[not found] <CALCETrU1RUzCV-abcDSAxrYJo=Ttrysz2Z0RL_kvzOx+eU6W4A@mail.gmail.com>
2014-08-16 20:43 ` Andy Lutomirski
2014-08-16 21:47 ` Serge E. Hallyn
2014-08-16 23:36 ` Josh Triplett
2014-08-17 4:00 ` Jan Kara
2014-08-17 21:50 ` Andy Lutomirski
2014-08-18 0:58 ` Serge E. Hallyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJfpegsoEGG2H1pFdBLAaosJhE8qbR69C9yikQHTd_egE001DA@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@amacapital.net \
--cc=serge@hallyn.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox