All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@google.com>
To: "Günther Noack" <gnoack3000@gmail.com>
Cc: Alejandro Colomar <alx+linux-man@kernel.org>, linux-man@vger.kernel.org
Subject: Re: [PATCH v2 6/6] man/man7/unix.7: ERRORS: Document EACCES, EAGAIN, EMSGSIZE, ENOSPC, and EPERM
Date: Mon, 16 Nov 2026 00:51:19 +0000	[thread overview]
Message-ID: <avpTfVwL7BEtKjeO@google.com> (raw)
In-Reply-To: <20261103202136.13574-7-gnoack3000@gmail.com>

On Tue, 03 Nov 2026 21:21:36 +0100, Günther Noack wrote:
> 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.
> 
> Cc: Kuniyuki Iwashima <kuniyu@google.com>
> Assisted-by: LLM
> Signed-off-by: Günther Noack <gnoack3000@gmail.com>

Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>

  reply	other threads:[~2026-11-16  0:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 20:21 [PATCH v2 0/6] {unix,socket,bind}.7: General Unix Domain Socket fixes Günther Noack
2026-11-03 20:21 ` [PATCH v2 1/6] man/man7/socket.7: SO_PEEK_OFF: This option is no longer specific to unix(7) Günther Noack
2026-11-03 20:21 ` [PATCH v2 2/6] man/man7/unix.7: SO_PEERCRED: Also works for SOCK_SEQPACKET Günther Noack
2026-11-03 20:21 ` [PATCH v2 3/6] man/man7/unix.7: SIOCINQ: Document behavior " Günther Noack
2026-11-16  0:48   ` Kuniyuki Iwashima
2026-11-03 20:21 ` [PATCH v2 4/6] man/man7/unix.7: Explain Abstract UDS scoping to the network namespace Günther Noack
2026-11-16  0:49   ` Kuniyuki Iwashima
2026-11-03 20:21 ` [PATCH v2 5/6] man/man2/bind.2: ERRORS: EACCES: Write permission on the directory is required Günther Noack
2026-11-03 20:21 ` [PATCH v2 6/6] man/man7/unix.7: ERRORS: Document EACCES, EAGAIN, EMSGSIZE, ENOSPC, and EPERM Günther Noack
2026-11-16  0:51   ` Kuniyuki Iwashima [this message]
2026-11-16 23:53   ` Alejandro Colomar
2026-11-06 12:54 ` [PATCH v2 0/6] {unix,socket,bind}.7: General Unix Domain Socket fixes Alejandro Colomar
2026-11-16 23:54   ` 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=avpTfVwL7BEtKjeO@google.com \
    --to=kuniyu@google.com \
    --cc=alx+linux-man@kernel.org \
    --cc=gnoack3000@gmail.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 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.