All of lore.kernel.org
 help / color / mirror / Atom feed
* proc.5: Update /proc/[pid]/task/[tid]/ example file
@ 2022-02-04 14:50 Tetsuo Handa
  0 siblings, 0 replies; only message in thread
From: Tetsuo Handa @ 2022-02-04 14:50 UTC (permalink / raw)
  To: Michael Kerrisk; +Cc: linux-fsdevel, linux-mm

Since all of the /proc/[pid]/task/[tid]/cwd files are allowed to have
different values (so that threads can use relative pathnames), using
cwd file as an example of "have the same value" is not appropriate.

Since threads in a multithreaded process are created using CLONE_VM
flag, all of the /proc/[pid]/task/[tid]/maps files must have the same
value. Therefore, let's use maps file as an example.
---
Should I use [PATCH] and S-o-b for changes not in kernel tree?
I didn't use them in order not to be caught by testing bot process.

 man5/proc.5 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man5/proc.5 b/man5/proc.5
index c6684620e..ea952b10f 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -2830,11 +2830,11 @@ file in the parent
 .I /proc/[pid]
 directory
 (e.g., in a multithreaded process, all of the
-.I task/[tid]/cwd
+.I task/[tid]/maps
 files will have the same value as the
-.I /proc/[pid]/cwd
+.I /proc/[pid]/maps
 file in the parent directory, since all of the threads in a process
-share a working directory).
+share the same memory space).
 For attributes that are distinct for each thread,
 the corresponding files under
 .I task/[tid]
-- 
2.18.4

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-02-04 14:50 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-04 14:50 proc.5: Update /proc/[pid]/task/[tid]/ example file Tetsuo Handa

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.