mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Chen Linxuan <chenlinxuan@uniontech.com>
Cc: Chen Linxuan <chenlinxuan@uniontech.com>,
	Yuan Haisheng <heysion@deepin.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: update the description of TracerPid in procfs.rst
Date: Tue, 15 Nov 2022 15:09:00 -0700	[thread overview]
Message-ID: <87v8nf98g3.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221102081517.19770-1-chenlinxuan@uniontech.com>

Chen Linxuan <chenlinxuan@uniontech.com> writes:

> When the tracer of process is outside of current pid namespace, field
> `TracerPid` in /proc/<pid>/status will be 0, too, just like this process
> not have been traced.
>
> This is because that function `task_pid_nr_ns` used to get the pid of
> tracer will return 0 in this situation.
>
> Co-authored-by: Yuan Haisheng <heysion@deepin.com>
> Signed-off-by: Chen Linxuan <chenlinxuan@uniontech.com>
> ---
>  Documentation/filesystems/proc.rst | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> index 898c99eae8e4..e98e0277f05e 100644
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -245,7 +245,8 @@ It's slow but very precise.
>   Ngid                        NUMA group ID (0 if none)
>   Pid                         process id
>   PPid                        process id of the parent process
> - TracerPid                   PID of process tracing this process (0 if not)
> + TracerPid                   PID of process tracing this process (0 if not, or
> +                             the tracer is outside of the current pid namespace)

Applied, thanks.

jon

      reply	other threads:[~2022-11-15 22:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  8:15 Chen Linxuan
2022-11-15 22:09 ` Jonathan Corbet [this message]

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=87v8nf98g3.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=chenlinxuan@uniontech.com \
    --cc=heysion@deepin.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®