mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Ziran Zhang <zhangcoder@yeah.net>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: clarify ptrace's effect on task_struct->parent
Date: Thu, 10 Sep 2026 14:54:04 +0200	[thread overview]
Message-ID: <aqKobFZ_a_Nvj_Wi@redhat.com> (raw)
In-Reply-To: <20260910041721.8135-1-zhangcoder@yeah.net>

On 09/10, Ziran Zhang wrote:
> The current comment for the parent field does not explain that it can be
> temporarily replaced by the tracer when the task is being ptraced.
> 
> This can lead to confusion, so clarify the comment to document this
> important behavior.
> 
> No functional change.
> 
> Signed-off-by: Ziran Zhang <zhangcoder@yeah.net>
> ---
>  include/linux/sched.h | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 705970d07..977859a63 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -1093,7 +1093,11 @@ struct task_struct {
>  	/* Real parent process: */
>  	struct task_struct __rcu	*real_parent;
>  
> -	/* Recipient of SIGCHLD, wait4() reports: */
> +	/*
> +	 * Recipient of SIGCHLD, wait4() reports. Normally the same as
> +	 * real_parent, but temporarily replaced by the tracer while the
> +	 * task is ptraced.
> +	 */
>  	struct task_struct __rcu	*parent;

Well. Not sure this comment needs to be updated...

Anyway, this looks like overdocumentation to me. Perhaps just

	/* Recipient of SIGCHLD, wait4() reports: ->real_parent or ptracer */

?

Oleg.


  reply	other threads:[~2026-09-10 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  4:17 Ziran Zhang
2026-09-10 12:54 ` Oleg Nesterov [this message]
2026-09-10 13:16   ` Ziran Zhang
2026-09-10 13:30 ` [PATCH v2] " Ziran Zhang

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=aqKobFZ_a_Nvj_Wi@redhat.com \
    --to=oleg@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=zhangcoder@yeah.net \
    /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®