From: Suren Baghdasaryan <surenb@google•com>
To: sfr@canb•auug.org.au
Cc: akpm@linux-foundation•org, ccross@google•com, surenb@google•com,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
kernel-team@android•com
Subject: [PATCH 1/1] docs: proc.rst: /proc/PID/maps: fix malformed table
Date: Tue, 23 Nov 2021 10:59:28 -0800 [thread overview]
Message-ID: <20211123185928.2513763-1-surenb@google.com> (raw)
Fix malformed table describing "pathname" values for mappings not
associated with a file.
Fixes: 2df148be9486 ("mm: add a field to store names for private anonymous memory")
Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
Signed-off-by: Suren Baghdasaryan <surenb@google•com>
---
Documentation/filesystems/proc.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 46c1f5243028..061744c436d9 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -426,14 +426,14 @@ with the memory region, as the case would be with BSS (uninitialized data).
The "pathname" shows the name associated file for this mapping. If the mapping
is not associated with a file:
- ======= ====================================
+ ============= ====================================
[heap] the heap of the program
[stack] the stack of the main process
[vdso] the "virtual dynamic shared object",
the kernel system call handler
-[anon:<name>] an anonymous mapping that has been
+ [anon:<name>] an anonymous mapping that has been
named by userspace
- ======= ====================================
+ ============= ====================================
or if empty, the mapping is anonymous.
--
2.34.0.rc2.393.gf8c9666880-goog
reply other threads:[~2021-11-23 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211123185928.2513763-1-surenb@google.com \
--to=surenb@google$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=ccross@google$(echo .)com \
--cc=kernel-team@android$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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