From: Alex Colomar <alx.manpages@gmail.com>
To: "Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack3000@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH 2/3] landlock.7: Document Landlock ABI v2 (file reparenting; kernel 5.19)
Date: Sat, 25 Feb 2023 02:06:16 +0100 [thread overview]
Message-ID: <0f3f221f-5724-97ea-a75f-790d44b145d2@gmail.com> (raw)
In-Reply-To: <5495bf9a0580a049bbe5a874c57202ba@mail.infomaniak.com>
[-- Attachment #1.1: Type: text/plain, Size: 1610 bytes --]
Hi Mickaël,
On 2/22/23 08:36, Mickaël Salaün wrote:
> On 2023-02-21T21:50:22.000+01:00, Günther Noack wrote:
>
> [...]
>
>> .SH VERSIONS
>> -Landlock was added in Linux 5.13.
>> +Landlock was introduced in Linux 5.13.
>> +.PP
>> +The availability of individual Landlock features is versioned through
>> +ABI levels:
>> +.TS
>> +box;
>> +ntb| ntb| lbx
>> +nt| nt| lbx.
>> +ABI Kernel Newly introduced access rights
>> +_ _ _
>> +1 5.13 LANDLOCK_ACCESS_FS_EXECUTE
>> +\^ \^ LANDLOCK_ACCESS_FS_WRITE_FILE
>> +\^ \^ LANDLOCK_ACCESS_FS_READ_FILE
>> +\^ \^ LANDLOCK_ACCESS_FS_READ_DIR
>> +\^ \^ LANDLOCK_ACCESS_FS_REMOVE_DIR
>> +\^ \^ LANDLOCK_ACCESS_FS_REMOVE_FILE
>> +\^ \^ LANDLOCK_ACCESS_FS_MAKE_CHAR
>> +\^ \^ LANDLOCK_ACCESS_FS_MAKE_DIR
>> +\^ \^ LANDLOCK_ACCESS_FS_MAKE_REG
>> +\^ \^ LANDLOCK_ACCESS_FS_MAKE_SOCK
>> +\^ \^ LANDLOCK_ACCESS_FS_MAKE_FIFO
>> +\^ \^ LANDLOCK_ACCESS_FS_MAKE_BLOCK
>> +\^ \^ LANDLOCK_ACCESS_FS_MAKE_SYM
>> +_ _ _
>> +2 5.19 LANDLOCK_ACCESS_FS_REFER
>> +.TE
>> +.PP
>
> A line break would be nice here.
.PP should be performing a line break. I didn't yet read the formatted
version, so maybe there's something wrong with the table, but from
inspection of the source it seems reasonable to me.
Cheers,
Alex
>
>> +To query the running kernel's Landlock ABI level, programs may pass
>
> s/level/version/
>
>> +the
>> +.B LANDLOCK_CREATE_RULESET_VERSION
>> +flag to
>> +.BR landlock_create_ruleset (2).
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-25 1:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 20:50 [PATCH 1/3] landlock.7: Move the warning about missing features into the CAVEATS section Günther Noack
2023-02-21 20:50 ` [PATCH 2/3] landlock.7: Document Landlock ABI v2 (file reparenting; kernel 5.19) Günther Noack
2023-02-22 7:01 ` Mickaël Salaün
2023-02-23 8:39 ` Günther Noack
2023-02-22 7:36 ` Mickaël Salaün
2023-02-23 8:48 ` Günther Noack
2023-02-25 1:10 ` Alex Colomar
2023-02-25 1:19 ` G. Branden Robinson
2023-02-25 1:29 ` Alex Colomar
2023-02-28 19:46 ` Günther Noack
2023-02-25 1:06 ` Alex Colomar [this message]
2023-02-22 7:45 ` Mickaël Salaün
2023-02-23 9:18 ` Günther Noack
2023-02-24 23:21 ` Alex Colomar
2023-02-28 20:21 ` Günther Noack
2023-02-21 20:50 ` [PATCH 3/3] landlock.7: Document Landlock ABI v3 (file truncation; kernel 6.2) Günther Noack
2023-02-22 8:04 ` Mickaël Salaün
2023-02-23 9:24 ` Günther Noack
2023-02-24 23:31 ` Alex Colomar
2023-02-28 20:29 ` Günther Noack
2023-02-24 23:04 ` [PATCH 1/3] landlock.7: Move the warning about missing features into the CAVEATS section Alex 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=0f3f221f-5724-97ea-a75f-790d44b145d2@gmail.com \
--to=alx.manpages@gmail.com \
--cc=gnoack3000@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mtk.manpages@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox