From: Max Chernoff <git@maxchernoff.ca>
To: Alejandro Colomar <alx@kernel.org>
Cc: Max Chernoff <git@maxchernoff.ca>, linux-man@vger.kernel.org
Subject: [PATCH v2 2/4] man/man5/proc_pid_smaps{,_rollup}.5: Add proc_pid_smaps_rollup(5)
Date: Mon, 14 Sep 2026 05:51:46 -0600 [thread overview]
Message-ID: <ddd2b68e220607cf6047e5ccff1d40702eefa47a.1789386106.git.git@maxchernoff.ca> (raw)
In-Reply-To: <cover.1789386106.git.git@maxchernoff.ca>
Link: <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=493b0e9d945fa9dfe96be93ae41b4ca4b6fdb317>
Signed-off-by: Max Chernoff <git@maxchernoff.ca>
---
man/man5/proc_pid_smaps.5 | 7 ++++++-
man/man5/proc_pid_smaps_rollup.5 | 1 +
2 files changed, 7 insertions(+), 1 deletion(-)
create mode 100644 man/man5/proc_pid_smaps_rollup.5
diff --git a/man/man5/proc_pid_smaps.5 b/man/man5/proc_pid_smaps.5
index 963136109ad8..51440cc13bf6 100644
--- a/man/man5/proc_pid_smaps.5
+++ b/man/man5/proc_pid_smaps.5
@@ -7,7 +7,7 @@
.\"
.TH proc_pid_smaps 5 (date) "Linux man-pages (unreleased)"
.SH NAME
-/proc/pid/smaps \- size of mapped memory regions
+/proc/pid/smaps, /proc/pid/smaps_rollup \- size of mapped memory regions
.SH DESCRIPTION
.TP
.IR /proc/ pid /smaps " (since Linux 2.6.14)"
@@ -125,5 +125,10 @@
file is present only if the
.B CONFIG_PROC_PAGE_MONITOR
kernel configuration option is enabled.
+.TP
+.IR /proc/ pid /smaps_rollup " (since Linux 4.14)"
+This file is similar to
+.IR /proc/ pid /smaps ,
+except all mappings are merged into a single synthetic entry.
.SH SEE ALSO
.BR proc (5)
diff --git a/man/man5/proc_pid_smaps_rollup.5 b/man/man5/proc_pid_smaps_rollup.5
new file mode 100644
index 000000000000..4b5f9eba0484
--- /dev/null
+++ b/man/man5/proc_pid_smaps_rollup.5
@@ -0,0 +1 @@
+.so man5/proc_pid_smaps.5
--
2.55.0
next prev parent reply other threads:[~2026-09-14 11:52 UTC|newest]
Thread overview: 11+ 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
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
2026-09-14 11:51 ` [PATCH v2 0/4] /proc/pid/smaps_rollup + CAP_MAC_ADMIN Max Chernoff
2026-09-14 11:51 ` [PATCH v2 1/4] man/man5/proc_pid_smaps.5: Add description Max Chernoff
2026-09-14 11:51 ` Max Chernoff [this message]
2026-09-14 11:51 ` [PATCH v2 3/4] 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-14 11:51 ` [PATCH v2 4/4] man/man7/capabilities.7: CAP_MAC_ADMIN allows setting undefined SELinux contexts Max Chernoff
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=ddd2b68e220607cf6047e5ccff1d40702eefa47a.1789386106.git.git@maxchernoff.ca \
--to=git@maxchernoff.ca \
--cc=alx@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).