Linux Manual Pages development
 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,
	 Alexander Mikhalitsyn <alexander@mihalicyn.com>,
	Christian Brauner <brauner@kernel.org>,
	 Eric Dumazet <edumazet@kernel.org>
Subject: Re: [PATCH v2 6/8] man/man7/unix.7: Document SO_PASSPIDFD, SO_PEERPIDFD, and SCM_PIDFD
Date: Mon, 16 Nov 2026 01:03:45 +0000	[thread overview]
Message-ID: <avpWXS_uoWG0ibxI@google.com> (raw)
In-Reply-To: <20261103202211.13820-7-gnoack3000@gmail.com>

On Tue, 03 Nov 2026 21:22:08 +0100, Günther Noack wrote:
> These were added in linux.git 5e2ff6704a27 (2023-06-12; "scm: add
> SO_PASSPIDFD and SCM_PIDFD") and 7b26952a91cf (2023-06-12; "net: core:
> add getsockopt SO_PEERPIDFD"), both in Linux 6.5.  They are the PID
> file descriptor counterparts of SO_PASSCRED/SCM_CREDENTIALS and
> SO_PEERCRED.
> 
> SO_PASSPIDFD
> 	sk_setsockopt() and sk_getsockopt() in net/core/sock.c handle it
> 	as a boolean flag for AF_UNIX sockets (EOPNOTSUPP otherwise).
> 	Like SO_PASSCRED, it triggers autobind, which was already
> 	mentioned in "Autobind feature".
> 
> SCM_PIDFD
> 	scm_pidfd_recv() in net/core/scm.c creates the PID file
> 	descriptor from scm->pid, which is the PID given in the sender's
> 	SCM_CREDENTIALS, or the sender's own PID by default.  The fd is
> 	created with O_CLOEXEC by pidfd_prepare().  If pidfd_prepare()
> 	fails, its negative error number is put into the cmsg data.
> 	Sending SCM_PIDFD is rejected by __scm_send() (EINVAL).
> 
> 	Since Linux 6.17, with c679d17d3f2d (2025-07-04; "af_unix:
> 	enable handing out pidfds for reaped tasks in SCM_PIDFD"),
> 	PIDFD_STALE is passed, so this also works for reaped processes.
> 	Before that, pidfd_prepare() returned -EINVAL for them.
> 
> SO_PEERPIDFD
> 	sk_getsockopt() returns a PID file descriptor for sk_peer_pid,
> 	or fails with ENODATA if there is none.
> 
> 	Since Linux 6.16, with 20b70e58961b (2025-04-28; "net, pidfs:
> 	enable handing out pidfds for reaped sk->sk_peer_pid"), this also
> 	works for reaped processes on AF_UNIX sockets.  Before that, it
> 	failed with EINVAL.
> 
> Cc: Alexander Mikhalitsyn <alexander@mihalicyn.com>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: Kuniyuki Iwashima <kuniyu@google.com>
> Cc: Eric Dumazet <edumazet@kernel.org>
> Assisted-by: LLM
> Signed-off-by: Günther Noack <gnoack3000@gmail.com>
> ---
>  man/man7/unix.7 | 100 ++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 100 insertions(+)
> 
> diff --git a/man/man7/unix.7 b/man/man7/unix.7
> index 93a0a335e791..140e77ea12ee 100644
> --- a/man/man7/unix.7
> +++ b/man/man7/unix.7
> @@ -311,6 +311,32 @@ .SS Socket options
>  .BR getsockopt (2)
>  is an integer boolean flag.
>  .TP
> +.BR SO_PASSPIDFD " (since Linux 6.5)"
> +Enabling this socket option causes receipt of a PID file descriptor
> +(see
> +.BR pidfd_open (2))
> +referring to the sending process in an
> +.B SCM_PIDFD
> +ancillary message in each subsequently received message
> +(see below).
> +.IP
> +As with
> +.BR SO_PASSCRED ,
> +when this option is set on a socket that is not bound to an address,
> +the socket is autobound to a unique name in the abstract namespace
> +when
> +.BR connect (2)
> +or
> +.BR sendmsg (2)
> +is called on it;
> +see "Autobind feature", below.
> +.IP
> +The value given as an argument to
> +.BR setsockopt (2)
> +and returned as the result of
> +.BR getsockopt (2)
> +is an integer boolean flag.
> +.TP
>  .B SO_PASSSEC
>  Enables receiving of the security context of the peer socket
>  in an ancillary message of type
> @@ -362,6 +388,43 @@ .SS Socket options
>  .B AF_UNIX
>  socket pairs created using
>  .BR socketpair (2).
> +.TP
> +.BR SO_PEERPIDFD " (since Linux 6.5)"
> +.\" commit 7b26952a91cf65ff1cc867a2382a8964d8c0ee7d

Same, otherwise looks good.

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

Thanks !

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

Thread overview: 16+ 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-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-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-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 [this message]
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
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=avpWXS_uoWG0ibxI@google.com \
    --to=kuniyu@google.com \
    --cc=alexander@mihalicyn.com \
    --cc=alx+linux-man@kernel.org \
    --cc=brauner@kernel.org \
    --cc=edumazet@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox