Documentation/filesystems/proc.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
From: Myro Demma <myro@myromyro.com>
Fix missing "from" in "prevent <pid> being reused" and
add spacing in vm_area_struct range notation for readability.
No functional changes.
Signed-off-by: Myro Demma <myro@myromyro.com>
---
Documentation/filesystems/proc.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 873761087f8d..d828006bd91c 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -118,7 +118,7 @@ PTRACE_MODE_ATTACH permissions; CAP_PERFMON capability does not grant access
to /proc/PID/mem for other processes.
Note that an open file descriptor to /proc/<pid> or to any of its
-contained files or subdirectories does not prevent <pid> being reused
+contained files or subdirectories does not prevent <pid> from being reused
for some other process in the event that <pid> exits. Operations on
open /proc/<pid> file descriptors corresponding to dead processes
never act on any new process that the kernel may, through chance, have
@@ -2199,7 +2199,7 @@ the process is maintaining. Example output::
| lr-------- 1 root root 64 Jan 27 11:24 400000-41a000 -> /usr/bin/ls
The name of a link represents the virtual memory bounds of a mapping, i.e.
-vm_area_struct::vm_start-vm_area_struct::vm_end.
+vm_area_struct::vm_start - vm_area_struct::vm_end.
The main purpose of the map_files is to retrieve a set of memory mapped
files in a fast way instead of parsing /proc/<pid>/maps or
--
2.54.0
Myro <mirademche@gmail.com> writes: > From: Myro Demma <myro@myromyro.com> > > Fix missing "from" in "prevent <pid> being reused" and > add spacing in vm_area_struct range notation for readability. > > No functional changes. > > Signed-off-by: Myro Demma <myro@myromyro.com> > --- > Documentation/filesystems/proc.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst > index 873761087f8d..d828006bd91c 100644 > --- a/Documentation/filesystems/proc.rst > +++ b/Documentation/filesystems/proc.rst > @@ -118,7 +118,7 @@ PTRACE_MODE_ATTACH permissions; CAP_PERFMON capability does not grant access > to /proc/PID/mem for other processes. > > Note that an open file descriptor to /proc/<pid> or to any of its > -contained files or subdirectories does not prevent <pid> being reused > +contained files or subdirectories does not prevent <pid> from being reused > for some other process in the event that <pid> exits. Operations on > open /proc/<pid> file descriptors corresponding to dead processes > never act on any new process that the kernel may, through chance, have > @@ -2199,7 +2199,7 @@ the process is maintaining. Example output:: > | lr-------- 1 root root 64 Jan 27 11:24 400000-41a000 -> /usr/bin/ls > > The name of a link represents the virtual memory bounds of a mapping, i.e. > -vm_area_struct::vm_start-vm_area_struct::vm_end. > +vm_area_struct::vm_start - vm_area_struct::vm_end. > Applied, thanks. jon
© 2016 - 2026 Red Hat, Inc.