From: Alejandro Colomar <alx@kernel.org>
To: Max Chernoff <git@maxchernoff.ca>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 2/3] man/man5/proc_pid_{smaps,smaps_rollup,maps}.5, man/man7/capabilities.7: CAP_PERFMON allows reading /proc/pid/{smaps,smaps_rollup,maps}
Date: Sat, 12 Sep 2026 15:39:37 +0200 [thread overview]
Message-ID: <aqVWA9eVr0jSxHGX@devuan> (raw)
In-Reply-To: <b239ee32ef7d0cbdc09c95f28034bb2426f72507.1789212041.git.git@maxchernoff.ca>
[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]
> Date: 2026-09-12 05:32:12-0600
> From: Max Chernoff <git@maxchernoff.ca>
>
> Link: <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0c555a3c1bc9114ad91422b941dcd29e02490687>
> Signed-off-by: Max Chernoff <git@maxchernoff.ca>
Reviewed-by: Alejandro Colomar <alx@kernel.org>
Cheers,
Alex
> ---
> man/man5/proc_pid_maps.5 | 5 ++++-
> man/man5/proc_pid_smaps.5 | 10 ++++++++++
> man/man7/capabilities.7 | 9 ++++++++-
> 3 files changed, 22 insertions(+), 2 deletions(-)
>
> diff --git a/man/man5/proc_pid_maps.5 b/man/man5/proc_pid_maps.5
> index 8783dbb3a89d..dcd455ea840c 100644
> --- a/man/man5/proc_pid_maps.5
> +++ b/man/man5/proc_pid_maps.5
> @@ -16,7 +16,10 @@
> .BR mmap (2)
> for some further information about memory mappings.
> .IP
> -Permission to access this file is governed by a ptrace access mode
> +Permission to access this file is governed by
> +.B CAP_PERFMON
> +(since Linux 6.15)
> +or a ptrace access mode
> .B PTRACE_MODE_READ_FSCREDS
> check;
> see
> diff --git a/man/man5/proc_pid_smaps.5 b/man/man5/proc_pid_smaps.5
> index 51440cc13bf6..d83521409375 100644
> --- a/man/man5/proc_pid_smaps.5
> +++ b/man/man5/proc_pid_smaps.5
> @@ -16,6 +16,16 @@
> .BR pmap (1)
> command displays similar information,
> in a form that may be easier for parsing.)
> +.IP
> +Permission to access this file is governed by
> +.B CAP_PERFMON
> +(since Linux 6.15)
> +or a ptrace access mode
> +.B PTRACE_MODE_READ_FSCREDS
> +check;
> +see
> +.BR ptrace (2).
> +.IP
> For each mapping there is a series of lines such as the following:
> .IP
> .in +4n
> diff --git a/man/man7/capabilities.7 b/man/man7/capabilities.7
> index eef074979f1b..bb8f6d9db433 100644
> --- a/man/man7/capabilities.7
> +++ b/man/man7/capabilities.7
> @@ -283,7 +283,14 @@
> call
> .BR perf_event_open (2);
> .IP \[bu]
> -employ various BPF operations that have performance implications.
> +employ various BPF operations that have performance implications;
> +.IP \[bu]
> +read the contents of
> +.IR /proc/ pid /maps,
> +.IR /proc/ pid /smaps,
> +and
> +.IR /proc/ pid /smaps_rollup
> +for all processes.
> .RE
> .PD
> .IP
> --
> 2.55.0
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-12 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 11:32 [PATCH 1/3] man/man5/proc_pid_smaps{,_rollup}.5: Add proc_pid_smaps_rollup(5) Max Chernoff
2026-09-12 11:32 ` [PATCH 2/3] man/man5/proc_pid_{smaps,smaps_rollup,maps}.5, man/man7/capabilities.7: CAP_PERFMON allows reading /proc/pid/{smaps,smaps_rollup,maps} Max Chernoff
2026-09-12 13:39 ` Alejandro Colomar [this message]
2026-09-12 11:32 ` [PATCH 3/3] man/man7/capabilities.7: CAP_MAC_ADMIN allows setting undefined SELinux contexts Max Chernoff
2026-09-12 13:41 ` Alejandro Colomar
2026-09-12 13:35 ` [PATCH 1/3] man/man5/proc_pid_smaps{,_rollup}.5: Add proc_pid_smaps_rollup(5) 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=aqVWA9eVr0jSxHGX@devuan \
--to=alx@kernel.org \
--cc=git@maxchernoff.ca \
--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