All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Christoph Anton Mitterer <calestyo@scientia.org>
Cc: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Subject: Re: [PATCH] open.2: Clarify different POSIX uses of EOPNOTSUPP and ENXIO
Date: Sun, 27 Aug 2023 21:41:17 +0200	[thread overview]
Message-ID: <87ttsk8e8y.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <979345cf576e86c42743ea48d797484fc41f8bf7.camel@scientia.org> (Christoph Anton Mitterer's message of "Fri, 25 Aug 2023 22:28:14 +0200")

* Christoph Anton Mitterer:

> @@ -1437,6 +1439,12 @@ with a value greater than or equal to 200809L or
>  with a value greater than or equal to 700.
>  In glibc 2.11 and earlier, one obtains the definitions by defining
>  .BR _GNU_SOURCE .
> +.PP
> +POSIX.1-2017 uses
> +.B EOPNOTSUPP
> +instead of
> +.B ENXIO
> +to indicate that the file is a UNIX domain socket.
>  .SH HISTORY
>  .TP
>  .BR open ()

To what degree is this dependent on the file system?  Does the VFS layer
restrict these error codes for anything else?  I don't think so.  Maybe
strictly speaking, the added wording is still accurate, but the
conclusion that ENXIO means socket would be incorrect draw, I think.

Thanks,
Florian


  reply	other threads:[~2023-08-27 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 20:28 [PATCH] open.2: Clarify different POSIX uses of EOPNOTSUPP and ENXIO Christoph Anton Mitterer
2023-08-27 19:41 ` Florian Weimer [this message]
2023-08-27 22:52   ` Christoph Anton Mitterer
2023-08-28 14:20   ` Matthew House

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=87ttsk8e8y.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=alx@kernel.org \
    --cc=calestyo@scientia.org \
    --cc=linux-man@vger.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.