From: "Günther Noack" <gnoack3000@gmail.com>
To: Alejandro Colomar <alx+linux-man@kernel.org>
Cc: "Günther Noack" <gnoack3000@gmail.com>,
linux-man@vger.kernel.org,
"Kuniyuki Iwashima" <kuniyu@google.com>
Subject: [PATCH v3 1/1] man/man7/unix.7: ERRORS: Document EACCES, EAGAIN, EMSGSIZE, ENOSPC, and EPERM
Date: Fri, 20 Nov 2026 14:25:35 +0100 [thread overview]
Message-ID: <20261120132535.20557-2-gnoack3000@gmail.com> (raw)
In-Reply-To: <20261120132535.20557-1-gnoack3000@gmail.com>
These are all returned directly from linux.git net/unix/af_unix.c:
EACCES
unix_find_bsd() checks path_permission(&path, MAY_WRITE) on the
socket file of the remote address. The rule was already described
in prose, but the error was not listed.
EAGAIN
unix_stream_connect() returns -EAGAIN when the listener's backlog
is full and the socket is nonblocking (there is no EINPROGRESS for
AF_UNIX). unix_dgram_sendmsg() returns -EAGAIN when the receiver's
queue is full and the send would block.
EMSGSIZE
unix_dgram_sendmsg() fails if 'len > sk->sk_sndbuf - 32'. This is
the limit described in "Sockets API".
ENOSPC
unix_autobind() fails when all 2^20 autobind names are taken.
EPERM
unix_dgram_connect() and unix_dgram_sendmsg() fail if
!unix_may_send(), that is, if the target datagram socket is
connected to a socket other than the caller's.
This is not something that the remote end normally does,
but it's a possible corner case.
For EADDRINUSE, simplify and shorten the wording.
Cc: Kuniyuki Iwashima <kuniyu@google.com>
Assisted-by: LLM
Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>
Signed-off-by: Günther Noack <gnoack3000@gmail.com>
---
man/man7/unix.7 | 36 ++++++++++++++++++++++++++++++++++--
1 file changed, 34 insertions(+), 2 deletions(-)
diff --git a/man/man7/unix.7 b/man/man7/unix.7
index b7b14793c794..61f06a74359b 100644
--- a/man/man7/unix.7
+++ b/man/man7/unix.7
@@ -676,9 +676,24 @@ .SS Ioctls
.\" and it may well change, probably best not to document this now.
.SH ERRORS
.TP
+.B EACCES
+Write permission is denied on the socket file
+specified as the remote address to
+.BR connect (2)
+or
+.BR sendto (2)
+(see "Pathname socket ownership and permissions", above).
+.TP
.B EADDRINUSE
-The specified local address is already in use or the filesystem socket
-object already exists.
+The specified local address is already in use
+or the file already exists.
+.TP
+.B EAGAIN
+The socket is nonblocking, and either
+.BR connect (2)
+was called on a stream or sequenced-packet socket
+and the backlog of the listening socket is full,
+or a datagram was sent to a socket whose receive queue is full.
.TP
.B EBADF
This error can occur for
@@ -715,6 +730,11 @@ .SH ERRORS
called on an already connected socket or a target address was
specified on a connected socket.
.TP
+.B EMSGSIZE
+The datagram to be sent is larger than the limit imposed by the
+.B SO_SNDBUF
+socket option (see "Sockets API", above).
+.TP
.B ENFILE
The system-wide limit on the total number of open files has been reached.
.TP
@@ -726,6 +746,11 @@ .SH ERRORS
.B ENOMEM
Out of memory.
.TP
+.B ENOSPC
+The socket was to be autobound,
+but all autobind addresses are in use
+(see "Autobind feature", above).
+.TP
.B ENOTCONN
Socket operation needs a target address, but the socket is not connected.
.TP
@@ -737,6 +762,13 @@ .SH ERRORS
The sender passed invalid credentials in the
.IR "struct ucred" .
.TP
+.B EPERM
+.BR connect (2)
+or
+.BR sendto (2)
+specified a datagram socket as the remote address,
+but that socket is connected to a different socket.
+.TP
.B EPIPE
Remote socket was closed on a stream socket.
If enabled, a
--
2.56.1
prev parent reply other threads:[~2026-11-20 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 13:25 [PATCH v3 0/1] {unix,socket,bind}.7: General Unix Domain Socket fixes Günther Noack
2026-11-20 13:25 ` Günther Noack [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=20261120132535.20557-2-gnoack3000@gmail.com \
--to=gnoack3000@gmail.com \
--cc=alx+linux-man@kernel.org \
--cc=kuniyu@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox