From: Christian Brauner <brauner@kernel.org>
To: Askar Safin <safinaskar@zohomail.com>
Cc: Aleksa Sarai <cyphar@cyphar.com>,
Alejandro Colomar <alx@kernel.org>,
"Michael T. Kerrisk" <mtk.manpages@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.cz>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
linux-api <linux-api@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v3 09/12] man/man2/open_tree.2: document "new" mount API
Date: Thu, 21 Aug 2025 13:33:24 +0200 [thread overview]
Message-ID: <20250821-adler-beute-47d721cde8a3@brauner> (raw)
In-Reply-To: <198cc623944.11ea2eb5d86377.2604785241030508275@zohomail.com>
On Thu, Aug 21, 2025 at 03:27:26PM +0400, Askar Safin wrote:
> man open_tree says:
> > mount propagation
> > (as described in
> > .BR mount_namespaces (7))
> > will not be applied to bind-mounts created by
> > .BR open_tree ()
> > until the bind-mount is attached with
> > .BR move_mount (2),
>
> It seems this is wrong, because this commit exists: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=06b1ce966e3f8bfef261c111feb3d4b33ede0cd8 .
> I'm not sure about this. (I didn't test this.)
No, it's correct. I reverted this because it broke userspace that relies
on this behavior.
next prev parent reply other threads:[~2025-08-21 11:33 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 20:39 [PATCH v3 00/12] man2: document "new" mount API Aleksa Sarai
2025-08-08 20:39 ` [PATCH v3 01/12] man/man2/statx.2: correctly document AT_NO_AUTOMOUNT Aleksa Sarai
2025-08-08 20:39 ` [PATCH v3 02/12] man/man2/mount_setattr.2: fix stray quote in SYNOPSIS Aleksa Sarai
2025-08-08 20:39 ` [PATCH v3 03/12] man/man2/mount_setattr.2: move mount_attr struct to mount_attr(2type) Aleksa Sarai
2025-08-08 20:39 ` [PATCH v3 04/12] man/man2/fsopen.2: document "new" mount API Aleksa Sarai
2025-08-08 20:39 ` [PATCH v3 05/12] man/man2/fspick.2: " Aleksa Sarai
2025-08-22 13:23 ` Askar Safin
2025-08-22 13:40 ` Aleksa Sarai
2025-08-25 16:22 ` Askar Safin
2025-08-08 20:39 ` [PATCH v3 06/12] man/man2/fsconfig.2: " Aleksa Sarai
2025-08-12 18:25 ` Aleksa Sarai
2025-08-21 9:42 ` Askar Safin
2025-08-21 11:44 ` Aleksa Sarai
2025-08-21 11:57 ` Askar Safin
2025-08-21 10:25 ` Askar Safin
2025-08-21 11:47 ` Aleksa Sarai
2025-08-08 20:39 ` [PATCH v3 07/12] man/man2/fsmount.2: " Aleksa Sarai
2025-08-12 9:16 ` Askar Safin
2025-08-12 14:33 ` Aleksa Sarai
2025-08-12 16:18 ` Aleksa Sarai
2025-08-20 9:55 ` Askar Safin
2025-08-20 10:38 ` Aleksa Sarai
2025-08-20 11:53 ` Askar Safin
2025-08-08 20:39 ` [PATCH v3 08/12] man/man2/move_mount.2: " Aleksa Sarai
2025-08-12 10:00 ` Askar Safin
2025-08-12 14:36 ` Aleksa Sarai
2025-08-20 11:18 ` Askar Safin
2025-08-08 20:39 ` [PATCH v3 09/12] man/man2/open_tree.2: " Aleksa Sarai
2025-08-21 11:27 ` Askar Safin
2025-08-21 11:33 ` Christian Brauner [this message]
2025-08-24 6:53 ` Askar Safin
2025-08-08 20:39 ` [PATCH v3 10/12] man/man2/mount_setattr.2: mirror opening sentence from fsopen(2) Aleksa Sarai
2025-08-08 20:39 ` [PATCH v3 11/12] man/man2/open_tree{,_attr}.2: document new open_tree_attr() API Aleksa Sarai
2025-08-08 20:39 ` [PATCH v3 12/12] man/man2/{fsconfig,mount_setattr}.2: add note about attribute-parameter distinction Aleksa Sarai
2025-08-09 15:04 ` [PATCH v3 00/12] man2: document "new" mount API Askar Safin
2025-08-09 15:11 ` Alejandro Colomar
2025-08-09 17:32 ` Aleksa Sarai
2025-08-11 11:27 ` Alejandro Colomar
2025-08-17 7:52 ` Askar Safin
2025-08-17 16:16 ` Aleksa Sarai
2025-08-17 18:50 ` Askar Safin
2025-08-18 5:46 ` Aleksa Sarai
2025-08-19 8:31 ` Christian Brauner
2025-08-19 8:50 ` Aleksa Sarai
2025-08-20 11:37 ` Askar Safin
2025-08-21 11:49 ` Aleksa Sarai
2025-08-21 12:14 ` Askar Safin
2025-08-21 14:21 ` Aleksa Sarai
2025-08-24 13:07 ` Askar Safin
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=20250821-adler-beute-47d721cde8a3@brauner \
--to=brauner@kernel.org \
--cc=alx@kernel.org \
--cc=cyphar@cyphar.com \
--cc=dhowells@redhat.com \
--cc=g.branden.robinson@gmail.com \
--cc=jack@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=safinaskar@zohomail.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;
as well as URLs for NNTP newsgroup(s).