[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1989db97e30.b71849c573511.8013418925525314426@zohomail.com>
Date: Tue, 12 Aug 2025 14:00:36 +0400
From: Askar Safin <safinaskar@...omail.com>
To: "Aleksa Sarai" <cyphar@...har.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 08/12] man/man2/move_mount.2: document "new" mount
API
move_mount for v2 contained this:
> Mounts cannot be moved beneath the rootfs
In v3 you changed this to this:
> Mount objects cannot be attached beneath the filesystem root
You made this phrase worse.
"Filesystem root" can be understood as "root of superblock".
So, please, change this to "root directory" or something.
> This would create a new bind-mount of /home/cyphar as attached mount object, and then attach
You meant "as detached mount object"
Also: I see that you addressed all my v2 comments. Thank you!
--
Askar Safin
https://types.pl/@safinaskar
Powered by blists - more mailing lists