linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: linux-man@vger.kernel.org, "Günther Noack" <gnoack3000@gmail.com>
Subject: Re: [PATCH v6 1/1] landlock.7: Explain the best-effort fallback mechanism in the example
Date: Tue, 18 Apr 2023 22:54:34 +0200	[thread overview]
Message-ID: <b2b27819-1af6-2ee4-f6fd-691277fd7d3b@gmail.com> (raw)
In-Reply-To: <1f68915c-daf6-83ba-3358-e090fca34909@digikod.net>


[-- Attachment #1.1: Type: text/plain, Size: 939 bytes --]

Hi Mickaël,

On 4/18/23 22:50, Mickaël Salaün wrote:
> Indeed, ENOTSUPP is a kernel error type, only EOPNOTSUPP should be used 
> to return error to user space. ENOTSUPP is not used by the kernel, it is 
> only defined by the libc:
> 
> # ifndef ENOTSUP
> #  define ENOTSUP		EOPNOTSUPP
> # endif
> 
> 

[...]

> 
> ENOTSUP doesn't exist in the kernel source, so it is legitimate that 
> Landlock and any other kernel interfaces use EOPNOTSUPP.  ENOTSUP should 
> then not replace EOPNOTSUPP for Landlock nor any other kernel interfaces.

That sounds reasonable.  It's a bit confusing that many man pages document
ENOTSUP (user-space).  I'll take this into account for when I see some
patch that touches one of those ENOTSUPs, and ask why, and maybe remove
them all in favor of EOPNOTSUPP.

Thanks,
Alex

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-04-18 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 15:59 [PATCH v6 0/1] landlock.7: Explain best-effort fallback in example Günther Noack
2023-04-14 15:59 ` [PATCH v6 1/1] landlock.7: Explain the best-effort fallback mechanism in the example Günther Noack
2023-04-14 16:35   ` Alejandro Colomar
2023-04-15  7:16     ` Günther Noack
2023-04-17 17:24       ` Alejandro Colomar
2023-04-17 20:54         ` Mickaël Salaün
2023-04-18 14:37           ` Alejandro Colomar
2023-04-18 20:50             ` Mickaël Salaün
2023-04-18 20:54               ` Alejandro Colomar [this message]
2023-04-18 20:55                 ` 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=b2b27819-1af6-2ee4-f6fd-691277fd7d3b@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).