[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025-08-20.1755686261-lurid-sleepy-lime-quarry-j42HLU@cyphar.com>
Date: Wed, 20 Aug 2025 20:38:48 +1000
From: Aleksa Sarai <cyphar@...har.com>
To: Askar Safin <safinaskar@...omail.com>
Cc: Alejandro Colomar <alx@...nel.org>,
"Michael T. Kerrisk" <mtk.manpages@...il.com>, Alexander Viro <viro@...iv.linux.org.uk>,
Jan Kara <jack@...e.cz>, "G. Branden Robinson" <g.branden.robinson@...il.com>,
linux-man <linux-man@...r.kernel.org>, linux-api <linux-api@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>,
David Howells <dhowells@...hat.com>, Christian Brauner <brauner@...nel.org>
Subject: Re: [PATCH v3 07/12] man/man2/fsmount.2: document "new" mount API
On 2025-08-20, Askar Safin <safinaskar@...omail.com> wrote:
> ---- On Tue, 12 Aug 2025 18:33:04 +0400 Aleksa Sarai <cyphar@...har.com> wrote ---
> > Unlike open_tree(2) with OPEN_TREE_CLONE, fsmount() can only be called
> > once in the lifetime of a filesystem context.
>
> Weird. open_tree doesn't get filesystem context as argument at all.
> I suggest just this:
>
> fsmount() can only be called
> once in the lifetime of a filesystem context.
The reason I wanted to include the comparison is that you can create
multiple mount objects from the same underlying object using
open_tree(2) but that's not possible with fsmount(2) (at least, not
without creating a new filesystem context each time).
--
Aleksa Sarai
Senior Software Engineer (Containers)
SUSE Linux GmbH
https://www.cyphar.com/
Download attachment "signature.asc" of type "application/pgp-signature" (266 bytes)
Powered by blists - more mailing lists