All of
 help / color / mirror / Atom feed
From: Tetsuo Handa <>
To: Michael Kerrisk <>
Cc: linux-fsdevel <>,
	linux-mm <>
Subject: proc.5: Update /proc/[pid]/task/[tid]/ example file
Date: Fri, 4 Feb 2022 23:50:12 +0900	[thread overview]
Message-ID: <> (raw)

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]
 (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]

                 reply	other threads:[~2022-02-04 14:50 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: proc.5: Update /proc/[pid]/task/[tid]/ example file' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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.