[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5hwvf2iikfly5etcjmjmwvvlwwjx24vcxtcx5ph2tyddjei7ea@wismq7gycqtq>
Date: Mon, 11 Aug 2025 13:27:01 +0200
From: Alejandro Colomar <alx@...nel.org>
To: Aleksa Sarai <cyphar@...har.com>
Cc: Askar Safin <safinaskar@...omail.com>,
"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 00/12] man2: document "new" mount API
Hi Aleksa,
On Sun, Aug 10, 2025 at 03:32:25AM +1000, Aleksa Sarai wrote:
> On 2025-08-09, Askar Safin <safinaskar@...omail.com> wrote:
> > I plan to do a lot of testing of "new" mount API on my computer.
> > It is quiet possible that I will find some bugs in these manpages during testing.
> > (I already found some, but I'm not sure.)
> > I think this will take 3-7 days.
> > So, Alejandro Colomar, please, don't merge this patchset until then.
>
> I don't plan to work on this again for the next week at least (I've
> already spent over a week on these docs -- writing, rewriting, and then
> rewriting once more for good measure; I've started seeing groff in my
> nightmares...), so I will go through review comments after you're done.
>
> There are some rough edges on these APIs I found while writing these
> docs, so I plan to fix those this cycle if possible (hopefully those
> aren't the bugs you said you found in the docs). Two of the fixes have
> already been merged in the vfs tree for 6.18 (the -ENODATA handling bug,
> as well as a bug in open_tree_attr() that would've let userspace trigger
> UAFs). (Once 6.18 is out, I will send a follow-up patchset to document
> the fixes.)
>
> FYI, I've already fixed the few ".BR \% FOO" typos. (My terminal font
> doesn't have a bold typeface, so when reviewing the rendered man-pages,
> mistakes involving .B are hard to spot.)
You can review in PDF if you want. See the pdfman(1) script under
src/bin/. It's quite portable:
$ cat src/bin/pdfman
#!/bin/bash
#
# Copyright, the authors of the Linux man-pages project
# SPDX-License-Identifier: GPL-3.0-or-later
set -Eeuo pipefail;
shopt -s lastpipe;
printf '%s\n' "${!#}.XXXXXX" \
| sed 's,.*/,,' \
| xargs mktemp -t \
| read -r tmp;
man -Tpdf "$@" >"$tmp";
xdg-open "$tmp";
It works essentially like man(1), so you can pass any man(7) file as its
argument to read it as a PDF.
(You may or may not have it available in your system, if your distro
packages a recent enough version of the project.)
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es/>
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists