mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phil Auld <pauld@redhat.com>
To: Jon Kohler <jon@nutanix.com>
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>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: add READ_ONCE to task_on_rq_queued
Date: Thu, 14 Nov 2024 14:14:19 -0500	[thread overview]
Message-ID: <20241114191419.GH471026@pauld.westford.csb> (raw)
In-Reply-To: <6A546A91-A80E-4D4C-9898-5EB792E19635@nutanix.com>

On Thu, Nov 14, 2024 at 06:59:14PM +0000 Jon Kohler wrote:
> 
> 
> > On Nov 14, 2024, at 1:52 PM, Phil Auld <pauld@redhat.com> wrote:
> > 
> > !-------------------------------------------------------------------|
> >  CAUTION: External Email
> > 
> > |-------------------------------------------------------------------!
> > 
> > On Thu, Nov 14, 2024 at 09:21:28AM -0700 Jon Kohler wrote:
> >> task_on_rq_queued read p->on_rq without READ_ONCE, though p->on_rq is
> >> set with WRITE_ONCE in {activate|deactivate}_task and smp_store_release
> >> in __block_task, and also read with READ_ONCE in task_on_rq_migrating.
> >> 
> >> Make all of these accesses pair together by adding READ_ONCE in the
> >> task_on_rq_queued.
> >> 
> >> Signed-off-by: Jon Kohler <jon@nutanix.com>
> >> ---
> >> kernel/sched/sched.h | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >> 
> >> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> >> index c03b3d7b320e..dbbe5ce0dd96 100644
> >> --- a/kernel/sched/sched.h
> >> +++ b/kernel/sched/sched.h
> >> @@ -2277,7 +2277,7 @@ static inline int task_on_cpu(struct rq *rq, struct task_struct *p)
> >> 
> >> static inline int task_on_rq_queued(struct task_struct *p)
> >> {
> >> - return p->on_rq == TASK_ON_RQ_QUEUED;
> >> + return READ_ONCE(p->on_rq) == TASK_ON_RQ_QUEUED;
> >> }
> >> 
> >> static inline int task_on_rq_migrating(struct task_struct *p)
> >> -- 
> >> 2.43.0
> >> 
> >> 
> > 
> > That looks right especially when seen with task_on_rq_migrating()
> > right below it, as you said.
> > 
> > Reviewed-by: Phil Auld <pauld@redhat.com>
> > 
> 
> Thanks Phil - note, I’ve got a v2 coming shortly as I’ve bungled the
> author and codeveloped tag from our internal version of this patch.
> 
> I’ll get that out, but it will be the exact same code.
>

You can just put my reviewed by on that one when you send it then.


Cheers,
Phil



> > 
> > Cheers,
> > Phil
> > -- 
> > 
> 

-- 


      reply	other threads:[~2024-11-14 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 16:21 Jon Kohler
2024-11-14 18:52 ` Phil Auld
2024-11-14 18:59   ` Jon Kohler
2024-11-14 19:14     ` Phil Auld [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=20241114191419.GH471026@pauld.westford.csb \
    --to=pauld@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jon@nutanix.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=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /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®