From: Askar Safin <safinaskar@gmail.com>
To: cyphar@cyphar.com
Cc: alx@kernel.org, brauner@kernel.org, dhowells@redhat.com,
g.branden.robinson@gmail.com, jack@suse.cz,
linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
mtk.manpages@gmail.com, safinaskar@zohomail.com,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH v4 05/10] man/man2/fsmount.2: document "new" mount API
Date: Mon, 22 Sep 2025 02:08:18 +0300 [thread overview]
Message-ID: <20250921230824.92612-1-safinaskar@gmail.com> (raw)
In-Reply-To: <20250919-new-mount-api-v4-5-1261201ab562@cyphar.com>
> Note that the unmount operation on close(2) is lazy—akin to calling umount2(2) with MOUNT_DETACH
MNT_DETACH, not MOUNT_DETACH
--
Askar Safin
next prev parent reply other threads:[~2025-09-21 23:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 1:59 [PATCH v4 00/10] man2: document "new" mount API Aleksa Sarai
2025-09-19 1:59 ` [PATCH v4 01/10] man/man2/mount_setattr.2: move mount_attr struct to mount_attr(2type) Aleksa Sarai
2025-09-19 16:04 ` Alejandro Colomar
2025-09-19 1:59 ` [PATCH v4 02/10] man/man2/fsopen.2: document "new" mount API Aleksa Sarai
2025-09-19 16:24 ` Alejandro Colomar
2025-09-19 21:19 ` Aleksa Sarai
2025-09-21 1:33 ` Aleksa Sarai
2025-09-21 8:39 ` Alejandro Colomar
2025-09-19 1:59 ` [PATCH v4 03/10] man/man2/fspick.2: " Aleksa Sarai
2025-09-21 8:53 ` Alejandro Colomar
2025-09-21 14:55 ` Aleksa Sarai
2025-09-21 15:17 ` Alejandro Colomar
2025-09-22 0:25 ` Askar Safin
2025-09-19 1:59 ` [PATCH v4 04/10] man/man2/fsconfig.2: " Aleksa Sarai
2025-09-21 9:26 ` Alejandro Colomar
2025-09-24 6:41 ` Aleksa Sarai
2025-09-24 8:52 ` Alejandro Colomar
2025-09-19 1:59 ` [PATCH v4 05/10] man/man2/fsmount.2: " Aleksa Sarai
2025-09-21 23:08 ` Askar Safin [this message]
2025-09-22 1:10 ` Askar Safin
2025-09-19 1:59 ` [PATCH v4 06/10] man/man2/move_mount.2: " Aleksa Sarai
2025-09-19 1:59 ` [PATCH v4 07/10] man/man2/open_tree.2: " Aleksa Sarai
2025-09-21 9:47 ` Alejandro Colomar
2025-09-22 10:09 ` Aleksa Sarai
2025-09-22 13:22 ` Alejandro Colomar
2025-09-24 1:34 ` Aleksa Sarai
2025-09-19 1:59 ` [PATCH v4 08/10] man/man2/mount_setattr.2: mirror opening sentence from fsopen(2) Aleksa Sarai
2025-09-21 9:50 ` Alejandro Colomar
2025-09-21 10:03 ` Aleksa Sarai
2025-09-21 10:19 ` Alejandro Colomar
2025-09-19 1:59 ` [PATCH v4 09/10] man/man2/open_tree{,_attr}.2: document new open_tree_attr() API Aleksa Sarai
2025-09-21 9:55 ` Alejandro Colomar
2025-09-24 6:31 ` Aleksa Sarai
2025-09-24 8:51 ` Alejandro Colomar
2025-09-19 1:59 ` [PATCH v4 10/10] man/man2/{fsconfig,mount_setattr}.2: add note about attribute-parameter distinction Aleksa Sarai
2025-09-19 12:23 ` Aleksa Sarai
2025-09-21 9:59 ` Alejandro Colomar
2025-09-22 1:06 ` Askar Safin
2025-09-21 2:43 ` [PATCH v4 00/10] man2: document "new" mount API Askar Safin
2025-09-21 9:58 ` Aleksa Sarai
2025-09-24 11:11 ` Aleksa Sarai
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=20250921230824.92612-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=alx@kernel.org \
--cc=brauner@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).