[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <198e20a3088.ef79515d27409.5672203109742133398@zohomail.com>
Date: Mon, 25 Aug 2025 20:22:55 +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 05/12] man/man2/fspick.2: document "new" mount API
---- On Fri, 22 Aug 2025 17:40:18 +0400 Aleksa Sarai <cyphar@...har.com> wrote ---
> On 2025-08-22, Askar Safin <safinaskar@...omail.com> wrote:
> > ---- On Sat, 09 Aug 2025 00:39:49 +0400 Aleksa Sarai <cyphar@...har.com> wrote ---
> > > +The above procedure is functionally equivalent to
> > > +the following mount operation using
> > > +.BR mount (2):
> >
> > This is not true.
> >
> > fspick adds options to superblock. It doesn't remove existing ones.
>
> fspick "copies the existing parameters" would be more accurate. I can
> reword this, but it's an example and I don't think it makes sense to add
> a large amount of clarifying text for each example.
I suggest adding "but mount(2) clears existing parameters here, and fspick/fsconfig doesn't".
--
Askar Safin
https://types.pl/@safinaskar
Powered by blists - more mailing lists