From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Günther Noack" <gnoack3000@gmail.com>,
"Mickaël Salaün" <mic@digikod.net>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 0/4] landlock.7: Code example improvements
Date: Wed, 19 Apr 2023 22:37:57 +0200 [thread overview]
Message-ID: <e7e34004-ab5c-68dd-da7b-1d275ccde190@gmail.com> (raw)
In-Reply-To: <20230419185443.7368-1-gnoack3000@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1321 bytes --]
Hi Günther!
On 4/19/23 20:54, Günther Noack wrote:
> Various improvements as pointed out by Mickaël Salaün in
> https://lore.kernel.org/linux-man/5d90e3b0-1577-7efd-03b8-f94b6e50fbc1@digikod.net/
>
> * Checking system call results differently, for consistency
> * Use constants for the compatibility table
> (I'm not very attached to the other solution)
> * Better wording for error message if Landlock unusable
> * Return instead of exit() if Landlock unusable
>
> Regarding the EOPNOTSUPP/ENOTSUP discussion, the consensus seems to be
> that EOPNOTSUPP is preferable, because that is the only of the two
> error codes that the kernel knows about.
>
> Günther Noack (4):
> landlock.7: Check syscall result with == -1 instead of <= 0
> landlock.7: Use LANDLOCK_* constants for compatibility table
> landlock.7: wfix: Error message wording in code example
> landlock.7: Return instead of exit() if Landlock is unusable
Thanks! Patch set applied. (I tweaked the commit messages a little
bit.)
Cheers,
Alex
>
> man7/landlock.7 | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
>
> base-commit: 6693a21cf73c502f2429b4ec07698130a2be9a93
--
<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-04-19 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 18:54 [PATCH 0/4] landlock.7: Code example improvements Günther Noack
2023-04-19 18:54 ` [PATCH 1/4] landlock.7: Check syscall result with == -1 instead of <= 0 Günther Noack
2023-04-19 18:54 ` [PATCH 2/4] landlock.7: Use LANDLOCK_* constants for compatibility table Günther Noack
2023-04-19 18:54 ` [PATCH 3/4] landlock.7: wfix: Error message wording in code example Günther Noack
2023-04-19 18:54 ` [PATCH 4/4] landlock.7: Return instead of exit() if Landlock is unusable Günther Noack
2023-04-19 20:37 ` Alejandro Colomar [this message]
2023-04-20 16:34 ` [PATCH 0/4] landlock.7: Code example improvements Mickaël Salaün
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=e7e34004-ab5c-68dd-da7b-1d275ccde190@gmail.com \
--to=alx.manpages@gmail.com \
--cc=gnoack3000@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mic@digikod.net \
/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;
as well as URLs for NNTP newsgroup(s).