[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250921024310.80511-1-safinaskar@gmail.com>
Date: Sun, 21 Sep 2025 05:43:10 +0300
From: Askar Safin <safinaskar@...il.com>
To: cyphar@...har.com
Cc: alx@...nel.org,
brauner@...nel.org,
dhowells@...hat.com,
g.branden.robinson@...il.com,
jack@...e.cz,
linux-api@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-man@...r.kernel.org,
mtk.manpages@...il.com,
safinaskar@...omail.com,
viro@...iv.linux.org.uk
Subject: Re: [PATCH v4 00/10] man2: document "new" mount API
Aleksa, thank you! Don't give up. We all need these manpages.
I see you didn't address some my previous notes.
* move_mount(2) still says "Mount objects cannot be attached beneath the filesystem root".
I suggest saying "root directory" or "root" or "root directory of the process" or just "/"
instead. But you may keep this phrase as is, of course.
* Docs for FSPICK_NO_AUTOMOUNT in fspick(2) are still wrong. They say that FSPICK_NO_AUTOMOUNT
affects all components of path. Similar thing applies to mount_setattr(2) and move_mount(2)
* open_tree(2) still says:
> If flags does not contain OPEN_TREE_CLONE, open_tree() returns a file descriptor
> that is exactly equivalent to one produced by openat(2) when called with the same dirfd and path.
This is not true if automounts are involved. I suggest adding "modulo automounts". But you may
keep everything, of course.
--
Askar Safin
Powered by blists - more mailing lists