Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Christian Brauner <christian.brauner@ubuntu.com>
To: David Howells <dhowells@redhat.com>
Cc: mtk.manpages@gmail.com, Miklos Szeredi <mszeredi@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Petr Vorel <pvorel@suse.cz>,
	linux-man <linux-man@vger.kernel.org>
Subject: Re: Setting mount propagation type in new mount API
Date: Mon, 18 May 2020 16:42:12 +0200	[thread overview]
Message-ID: <20200518144212.xpfjlajgwzwhlq7r@wittgenstein> (raw)
In-Reply-To: <909768.1589812234@warthog.procyon.org.uk>

On Mon, May 18, 2020 at 03:30:34PM +0100, David Howells wrote:
> Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
> 
> > I've been looking at the new mount API (fsopen(), fsconfig(),
> > fsmount(), move_mount(), etc.) and among the details that remain
> > mysterious to me is this: how does one set the propagation type
> > (private/shared/slave/unbindable) of a new mount and change the
> > propagation type of an existing mount?
> 
> Christian said he was going to have a go at writing mount_setattr().  It's not
> trivial as it has to be able to handle AT_RECURSIVE.

Right, I've put this on my roadmap now. It's becoming more urgent for us
too since I've already switched over a few bits to the new mount api to
make use of detached/anonymous mounts.
I've planned to start working on a version early next week.

Christian

      reply	other threads:[~2020-05-18 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 11:40 Michael Kerrisk (man-pages)
2020-05-15 13:04 ` Miklos Szeredi
2020-05-15 13:18   ` Miklos Szeredi
2020-05-18 14:30 ` David Howells
2020-05-18 14:42   ` Christian Brauner [this message]

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=20200518144212.xpfjlajgwzwhlq7r@wittgenstein \
    --to=christian.brauner@ubuntu.com \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=mtk.manpages@gmail.com \
    --cc=pvorel@suse.cz \
    --subject='Re: Setting mount propagation type in new mount API' \
    /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

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).