From: Alejandro Colomar <alx@kernel.org>
To: Askar Safin <safinaskar@gmail.com>
Cc: linux-man@vger.kernel.org, Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] man/man3/errno.3: clarify ENOTSUP and EOPNOTSUPP
Date: Thu, 28 May 2026 00:59:44 +0200 [thread overview]
Message-ID: <ahd3SmZZqnzP0-O2@devuan> (raw)
In-Reply-To: <20260527181549.2237547-1-safinaskar@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1664 bytes --]
Hi Askar,
On 2026-05-27T18:15:48+0000, Askar Safin wrote:
> As revealed by Christian Brauner recently
> ( https://lore.kernel.org/all/20260527-fotowettbewerb-abwinken-einfach-83db3411945b@brauner/ ),
> EOPNOTSUPP is widely used on Linux to mean "Operation not supported",
> as opposed to "Operation not supported on socket".
>
> Also, as seen in POSIX issue 8:
> https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/errno.h.html
> POSIX doesn't require ENOTSUP and EOPNOTSUPP to be distinct, so
> let's update that, too.
>
> Signed-off-by: Askar Safin <safinaskar@gmail.com>
I've applied the patch; thanks!
Have a lovely night!
Alex
> ---
> man/man3/errno.3 | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/man/man3/errno.3 b/man/man3/errno.3
> index a070dab..fdd2710 100644
> --- a/man/man3/errno.3
> +++ b/man/man3/errno.3
> @@ -477,13 +477,14 @@ Name not unique on network.
> No such device or address (POSIX.1-2001).
> .TP
> .B EOPNOTSUPP
> -Operation not supported on socket (POSIX.1-2001).
> +Operation not supported (POSIX.1-2001).
> +According to POSIX.1 this is "Operation not supported on socket",
> +but on Linux it effectively means just "Operation not supported".
> .IP
> .RB ( ENOTSUP
> and
> .B EOPNOTSUPP
> -have the same value on Linux, but
> -according to POSIX.1 these error values should be distinct.)
> +have the same value on Linux.)
> .TP
> .B EOVERFLOW
> Value too large to be stored in data type (POSIX.1-2001).
>
> base-commit: 9a4bfd0e50745c2649b6291db40b58e37c9c1c6b
> --
> 2.47.3
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-05-27 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 18:15 [PATCH] man/man3/errno.3: clarify ENOTSUP and EOPNOTSUPP Askar Safin
2026-05-27 22:59 ` Alejandro Colomar [this message]
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=ahd3SmZZqnzP0-O2@devuan \
--to=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=safinaskar@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