From: David Howells <dhowells@redhat.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: dhowells@redhat.com,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Christian Brauner <christian@brauner.io>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: Feature bug with the new mount API: no way of doing read only bind mounts
Date: Thu, 21 Nov 2019 15:04:32 +0000 [thread overview]
Message-ID: <5624.1574348672@warthog.procyon.org.uk> (raw)
In-Reply-To: <20191121145410.lxrkxzmfioxbll37@wittgenstein>
Christian Brauner <christian.brauner@ubuntu.com> wrote:
> Also, I thought we've agreed a while back that the flags would move into
> a struct since mount is gaining flags quickly too. :)
I think we did agree that. What I just wrote in the email was more of a
tentative illustration.
David
next prev parent reply other threads:[~2019-11-21 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 0:11 Feature bug with the new mount API: no way of doing read only bind mounts James Bottomley
2019-11-21 8:10 ` David Howells
2019-11-21 14:54 ` Christian Brauner
2019-11-21 15:00 ` James Bottomley
2019-11-21 15:04 ` David Howells [this message]
2019-11-21 16:15 ` James Bottomley
2019-11-27 20:32 ` James Bottomley
2019-11-27 20:33 ` [RFC 1/6] logger: add a limited buffer logging facility James Bottomley
2019-11-27 20:34 ` [RFC 2/6] configfd: add generic file descriptor based configuration parser James Bottomley
2019-11-27 20:35 ` [RFC 3/6] configfd: syscall: wire up configfd syscalls James Bottomley
2019-11-27 20:36 ` [RFC 4/6] fs: implement fsconfig via configfd James Bottomley
2019-11-27 20:37 ` [RFC 5/6] fs: expose internal interfaces open_detached_copy and do_reconfigure_mount James Bottomley
2019-11-27 20:38 ` [RFC 6/6] fs: bind: add configfs type for bind mounts James Bottomley
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=5624.1574348672@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=christian.brauner@ubuntu.com \
--cc=christian@brauner.io \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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;
as well as URLs for NNTP newsgroup(s).