All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Günther Noack" <gnoack@google.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
	linux-security-module@vger.kernel.org,
	"Tahera Fahimi" <fahimitahera@gmail.com>,
	"Tanya Agarwal" <tanyaagarwal25699@gmail.com>,
	"Daniel Burgener" <dburgener@linux.microsoft.com>,
	tools@kernel.org, linux-doc@vger.kernel.org,
	linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] landlock: Minor typo and grammar fixes in IPC scoping documentation
Date: Wed, 26 Feb 2025 22:38:05 +0100	[thread overview]
Message-ID: <Z7-JvY4DP-CswCyF@google.com> (raw)
In-Reply-To: <5xijgm2hkedx2tu6fjt67ozf2rmvjz6z4zvvcvokymc3hlc6of@xqpnvf23ia2s>

Hello!

On Wed, Feb 26, 2025 at 09:57:58PM +0100, Alejandro Colomar wrote:
> On Wed, Feb 26, 2025 at 08:24:22PM +0000, Günther Noack wrote:
> > On Wed, Feb 12, 2025 at 04:06:06PM +0100, Alejandro Colomar wrote:
> > > So you could really use man9 for internal Landlock stuff.  Even if I
> > > think generated documentation isn't ideal, it's better than nothing.
> > > Being able to use man(1) for reading kernel documentation would still be
> > > a nice feature.
> > > 
> > > And while I can't run all the linters that I run on hand-written docs on
> > > generated pages (because generated source necessarily triggers many
> > > false positives), I could still run some, which would trigger some
> > > accidents in the docs, and would also detect bugs in the software
> > > translating the docs from one language to another.
> > > 
> > > So, I'd still recommend you considering man9.
> > 
> > This is different to the BPF helpers; Landlock's existing man pages document
> > user space APIs, and the largest part of the kernel-side .rst documentation for
> > Landlock also covers only user space.
> 
> Huh!  Why does the kernel duplicate what's already in the manual pages?

That duplication is *precisely* the problem we have in Landlock. :)

(If you look at the patch series I've been sending with both the patches sent to
linux-security-modules@ and linux-man@, you'll see the duplication,
e.g. https://lore.kernel.org/all/20250226211814.31420-2-gnoack@google.com/)

Documentation of user space APIs is not unusual in the kernel documentation,
there is the entire subdirectory Documentation/userspace-api for it.

—Günther

  reply	other threads:[~2025-02-26 21:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 15:44 [PATCH 1/2] landlock: Minor typo and grammar fixes in IPC scoping documentation Günther Noack
2025-01-24 15:44 ` [PATCH 2/2] landlock: Clarify " Günther Noack
2025-01-24 15:58   ` Daniel Burgener
2025-01-24 15:59   ` Günther Noack
2025-02-02 12:51     ` Alejandro Colomar
2025-02-26 20:52       ` Günther Noack
2025-02-26 21:21         ` Alejandro Colomar
2025-02-11 15:20     ` Mickaël Salaün
2025-01-24 16:37 ` [PATCH man 1/3] landlock.7: Update description of Landlock rules Günther Noack
2025-01-24 16:37 ` [PATCH man 2/3] landlock.7: Move over documentation for ABI version 6 Günther Noack
2025-01-24 16:37 ` [PATCH man 3/3] landlock.7: Update wording in line with kernel side proposal Günther Noack
2025-02-11 15:17 ` [PATCH 1/2] landlock: Minor typo and grammar fixes in IPC scoping documentation Mickaël Salaün
2025-02-11 15:27   ` Alejandro Colomar
2025-02-11 15:53     ` Mickaël Salaün
2025-02-11 16:13       ` Alejandro Colomar
2025-02-11 18:08         ` G. Branden Robinson
2025-02-12 15:15           ` Alejandro Colomar
2025-02-11 19:24         ` Mickaël Salaün
2025-02-12 15:06           ` Alejandro Colomar
2025-02-26 20:24             ` Günther Noack
2025-02-26 20:57               ` Alejandro Colomar
2025-02-26 21:38                 ` Günther Noack [this message]
2025-02-26 21:51                   ` Alejandro Colomar

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=Z7-JvY4DP-CswCyF@google.com \
    --to=gnoack@google.com \
    --cc=alx@kernel.org \
    --cc=dburgener@linux.microsoft.com \
    --cc=fahimitahera@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=tanyaagarwal25699@gmail.com \
    --cc=tools@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.