All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.co.jp>
To: Michael Kerrisk <mtk.manpages@gmail.com>,
	Alejandro Colomar <alx.manpages@gmail.com>
Cc: Benjamin Herrenschmidt <benh@amazon.com>,
	Kuniyuki Iwashima <kuniyu@amazon.co.jp>,
	Kuniyuki Iwashima <kuni1840@gmail.com>,
	<linux-man@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: [PATCH] unix.7: Add a description for ENFILE.
Date: Wed, 29 Sep 2021 10:38:41 +0900	[thread overview]
Message-ID: <20210929013841.1694-1-kuniyu@amazon.co.jp> (raw)

When creating UNIX domain sockets, the kernel used to return -ENOMEM on
error where it should return -ENFILE.  The behaviour has been wrong since
2.2.4 and fixed in the recent commit f4bd73b5a950 ("af_unix: Return errno
instead of NULL in unix_create1().").

Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.co.jp>
---
Note to maintainers of man-pages, the commit is merged in the net tree [0]
but not in the Linus' tree yet.

[0]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=f4bd73b5a950
---
 man7/unix.7 | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/man7/unix.7 b/man7/unix.7
index 6d30b25cd..2dc96fea1 100644
--- a/man7/unix.7
+++ b/man7/unix.7
@@ -721,6 +721,9 @@ invalid state for the applied operation.
 called on an already connected socket or a target address was
 specified on a connected socket.
 .TP
+.B ENFILE
+The system-wide limit on the total number of open files has been reached.
+.TP
 .B ENOENT
 The pathname in the remote address specified to
 .BR connect (2)
-- 
2.30.2


             reply	other threads:[~2021-09-29  1:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29  1:38 Kuniyuki Iwashima [this message]
2021-10-02 17:44 ` [PATCH] unix.7: Add a description for ENFILE Alejandro Colomar (man-pages)
2021-10-02 17:56   ` Kuniyuki Iwashima
2021-10-02 18:10     ` Alejandro Colomar (man-pages)
2021-10-02 18:12 ` Alejandro Colomar (man-pages)
2021-10-02 18:47   ` Kuniyuki Iwashima

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=20210929013841.1694-1-kuniyu@amazon.co.jp \
    --to=kuniyu@amazon.co.jp \
    --cc=alx.manpages@gmail.com \
    --cc=benh@amazon.com \
    --cc=kuni1840@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=netdev@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.