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,  Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH v2 7/8] man/man7/unix.7: Document SO_PASSRIGHTS
Date: Mon, 16 Nov 2026 01:02:25 +0000	[thread overview]
Message-ID: <avpVmvkSH0DD_pPe@google.com> (raw)
In-Reply-To: <20261103202211.13820-8-gnoack3000@gmail.com>

On Tue, 03 Nov 2026 21:22:09 +0100, Günther Noack wrote:
> SO_PASSRIGHTS was added in linux.git 77cbe1a6d873 (2025-05-23;
> "af_unix: Introduce SO_PASSRIGHTS."), in Linux 6.16.  It lets a
> receiver refuse file descriptors passed with SCM_RIGHTS, so that an
> untrusted peer cannot leave it with file descriptors whose final
> close() blocks for a long time (for example, a file on a hung NFS
> mount or a FUSE-controlled file).
> 
> The option is enabled by default (unix_create1()).  When the receiving
> socket has it disabled, unix_dgram_sendmsg(), unix_stream_sendmsg(),
> and queue_oob() fail with EPERM if the message carries file
> descriptors.  The check happens at send time, so messages that are
> already queued are unaffected.
> 
> Also add the new EPERM case to ERRORS.
> 
> Link: [1] <https://uapi-group.org/kernel-features/#disabling-reception-of-scm_rights-for-af_unix-sockets>
> Link: [2] <https://lore.kernel.org/all/20250519205820.66184-1-kuniyu@amazon.com/>
> Cc: Kuniyuki Iwashima <kuniyu@google.com>
> Cc: Willem de Bruijn <willemb@google.com>
> Assisted-by: LLM
> Signed-off-by: Günther Noack <gnoack3000@gmail.com>
> ---
>  man/man7/unix.7 | 37 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 37 insertions(+)
> 
> diff --git a/man/man7/unix.7 b/man/man7/unix.7
> index 140e77ea12ee..1b4cd242657d 100644
> --- a/man/man7/unix.7
> +++ b/man/man7/unix.7
> @@ -337,6 +337,35 @@ .SS Socket options
>  .BR getsockopt (2)
>  is an integer boolean flag.
>  .TP
> +.BR SO_PASSRIGHTS " (since Linux 6.16)"
> +.\" commit 77cbe1a6d8730a07f99f9263c2d5f2304cf5e830

Wasn't the plan to move SHA1 to commit message ?

otherwise looks good.

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

  reply	other threads:[~2026-11-16  1:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 20:22 [PATCH v2 0/8] unix.7: Socket Options and SCM_* fixes Günther Noack
2026-11-03 20:22 ` [PATCH v2 1/8] man/man7/unix.7: ERRORS: ETOOMANYREFS: Fix the conditions Günther Noack
2026-11-06 13:00   ` Alejandro Colomar
2026-11-03 20:22 ` [PATCH v2 2/8] man/man7/unix.7: Multiple same-typed SCM_* messages may be sent in one message Günther Noack
2026-11-16  0:52   ` Kuniyuki Iwashima
2026-11-18  0:59     ` Alejandro Colomar
2026-11-03 20:22 ` [PATCH v2 3/8] man/man7/unix.7: Autobind: Clarify when it happens, and mention SO_PASSPIDFD Günther Noack
2026-11-16  0:53   ` Kuniyuki Iwashima
2026-11-18  1:06     ` Alejandro Colomar
2026-11-03 20:22 ` [PATCH v2 4/8] man/man7/unix.7: SCM_SECURITY: Generalize to other LSMs, not just SELinux Günther Noack
2026-11-16  0:55   ` Kuniyuki Iwashima
2026-11-16  7:35     ` Günther Noack
2026-11-18  1:15       ` Alejandro Colomar
2026-11-18  1:13   ` Alejandro Colomar
2026-11-03 20:22 ` [PATCH v2 5/8] man/man7/unix.7: SO_PASSSEC: wfix Günther Noack
2026-11-03 20:22 ` [PATCH v2 6/8] man/man7/unix.7: Document SO_PASSPIDFD, SO_PEERPIDFD, and SCM_PIDFD Günther Noack
2026-11-16  1:03   ` Kuniyuki Iwashima
2026-11-03 20:22 ` [PATCH v2 7/8] man/man7/unix.7: Document SO_PASSRIGHTS Günther Noack
2026-11-16  1:02   ` Kuniyuki Iwashima [this message]
2026-11-03 20:22 ` [PATCH v2 8/8] man/man7/unix.7: Remove mentions of "namespace" in the general sense Günther Noack
2026-11-16  0:59   ` 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=avpVmvkSH0DD_pPe@google.com \
    --to=kuniyu@google.com \
    --cc=alx+linux-man@kernel.org \
    --cc=gnoack3000@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=willemb@google.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 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.