ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Mount API?
Date: Sun, 17 Aug 2014 21:03:52 -0700	[thread overview]
Message-ID: <CALCETrW53hiZpFH4J+UsE_tX6i_cTmfth5xHtOzw8uPGGEbf4Q@mail.gmail.com> (raw)
In-Reply-To: <20140818040014.GA10623@mail.hallyn.com>

[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]

On Aug 17, 2014 11:00 PM, "Serge E. Hallyn" <serge@hallyn.com> wrote:
>
> Quoting Eric W. Biederman (ebiederm@xmission.com):
> >
> > Serge E. Hallyn <serge@hallyn.com> writes:
> > > Quoting Andy Lutomirski (luto at amacapital.net):
> > > > ISTR Eric Biederman mentioned this, but I don't know whether he's
> > > > volunteering or whether he'll be there.
> > > >
> > > > I could try to write it, but my VFS track record is pretty bad.
> > > > On Aug 16, 2014 9:00 PM, "Jan Kara" <jack at suse.cz> wrote:
> > > >
> > > > > On Sat 16-08-14 13:43:40, Andy Lutomirski wrote:
> > > > > > Is anyone interested in discussing a new mount API in the
unconference
> > > > > > track?
> > > > > >
> > > > > > Think bindmountat, etc.
> > > > >   We can discuss however will there be anyone who's going to
write the
> > > > > code? I know Miklos Szeredi was looking into that but it didn't
go anywhere
> > > > > AFAIK and he won't be at KS/LinuxCon. And I'm not sure if Al will
be at the
> > > > > conference..
> > >
> > > I'm quite certain Eric will at least be at the venue.  Eric?
> >
> > I am here and I will be here all week.
> >
> > With respect to bind mounts I was mentioning a patch that someone
> > was actively working on a week or two ago to allow at least the
read-only
> > flag to be specified when a bind mount is created.
> >
> > For a whole new clean mount API I don't know.  I do think it would be
> > productive for us to get together and talk.  Weather that is at the
> > container session on Friday or elswhere I don't know.
>
> If Al isn't there on M-T, then Friday works great for me.

I'll be gone then.  Oh, well.

>
> thanks,
> -serge

[-- Attachment #2: Type: text/html, Size: 2505 bytes --]

  reply	other threads:[~2014-08-18  4:03 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 [this message]
2014-08-18  8:35     ` Miklos Szeredi
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=CALCETrW53hiZpFH4J+UsE_tX6i_cTmfth5xHtOzw8uPGGEbf4Q@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=serge@hallyn.com \
    /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