linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Ben Segall <bsegall@google.com>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>, Mel Gorman <mgorman@suse.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH] ptrace: fix ptrace vs tasklist_lock race on PREEMPT_RT.
Date: Mon, 14 Mar 2022 19:54:30 +0100	[thread overview]
Message-ID: <20220314185429.GA30364@redhat.com> (raw)
In-Reply-To: <Yh/b19JikC+Vnm8i@linutronix.de>

I never really understood ->saved_state logic. Will read this patch
tomorrow, but at first glance this patch doesn't solve all problems.

On 03/02, Sebastian Andrzej Siewior wrote:
>
> +static inline bool __task_state_match_eq(struct task_struct *tsk, long state)
> +{
> +	bool match = false;
> +
> +	if (READ_ONCE(tsk->__state) == state)
> +		match = true;
> +	else if (tsk->saved_state == state)
> +		match = true;
> +	return match;
> +}

...

> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -3239,7 +3239,8 @@ unsigned long wait_task_inactive(struct task_struct *p, unsigned int match_state
>  		 * is actually now running somewhere else!
>  		 */
>  		while (task_running(rq, p)) {
> -			if (match_state && unlikely(READ_ONCE(p->__state) != match_state))
> +			if (match_state &&
> +			    unlikely(!task_state_match_eq(p, match_state)))
>  				return 0;

So wait_task_inactive() can return 0 but the task can run after that, right?
This is not what we want...

Oleg.


  parent reply	other threads:[~2022-03-14 18:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 21:04 [PATCH] ptrace: fix ptrace vs tasklist_lock race on PREEMPT_RT Sebastian Andrzej Siewior
2022-03-14  9:27 ` Sebastian Andrzej Siewior
2022-03-14 18:54 ` Oleg Nesterov [this message]
2022-03-15  8:31   ` Sebastian Andrzej Siewior
2022-03-15 14:29     ` Oleg Nesterov
2022-03-16  8:23       ` Sebastian Andrzej Siewior
2022-03-31 14:25       ` [PATCH v2] " Sebastian Andrzej Siewior
2022-04-04 16:13         ` Oleg Nesterov
2022-04-05  8:34           ` Oleg Nesterov
2022-04-05 10:10         ` Peter Zijlstra
2022-04-05 10:29           ` Oleg Nesterov
2022-04-05 11:28             ` Peter Zijlstra
2022-04-07 12:13               ` Peter Zijlstra
2022-04-07 17:51                 ` Eric W. Biederman
2022-04-07 22:50                 ` Eric W. Biederman
2022-04-08  9:09                   ` Peter Zijlstra
2022-04-08 19:40                     ` Eric W. Biederman
2022-04-08 20:06                       ` Peter Zijlstra
2022-04-11 11:35                         ` Peter Zijlstra
2022-04-11 13:44                           ` Eric W. Biederman
2022-04-11 17:07                             ` Peter Zijlstra
2022-04-12 11:59                               ` Peter Zijlstra

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=20220314185429.GA30364@redhat.com \
    --to=oleg@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).