mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Vincent Donnefort <Vincent.Donnefort@arm.com>,
	mingo@redhat.com, linux-kernel@vger.kernel.org,
	dietmar.eggemann@arm.com, Valentin.Schneider@arm.com,
	jing-ting.wu@mediatek.com
Subject: Re: [PATCH] sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain()
Date: Mon, 8 Nov 2021 12:19:23 +0100	[thread overview]
Message-ID: <YYkHu8kkp9q9/QPP@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKfTPtAQTCqhbaW90EiyerPM2x-==cX3Xodq+nAymVK_U=45vA@mail.gmail.com>

On Fri, Nov 05, 2021 at 04:08:33PM +0100, Vincent Guittot wrote:
> On Thu, 4 Nov 2021 at 18:52, Vincent Donnefort
> <vincent.donnefort@arm.com> wrote:
> >
> > Nothing protects the access to the per_cpu variable sd_llc_id. When testing
> > the same CPU (i.e. this_cpu == that_cpu), a race condition exists with
> > update_top_cache_domain(). One scenario being:
> >
> >               CPU1                            CPU2
> >   ==================================================================
> >
> >   per_cpu(sd_llc_id, CPUX) => 0
> >                                     partition_sched_domains_locked()
> >                                       detach_destroy_domains()
> >   cpus_share_cache(CPUX, CPUX)          update_top_cache_domain(CPUX)
> >     per_cpu(sd_llc_id, CPUX) => 0
> >                                           per_cpu(sd_llc_id, CPUX) = CPUX
> >     per_cpu(sd_llc_id, CPUX) => CPUX
> >     return false
> >
> > ttwu_queue_cond() wouldn't catch smp_processor_id() == cpu and the result
> > is a warning triggered from ttwu_queue_wakelist().
> >
> > Avoid a such race in cpus_share_cache() by always returning true when
> > this_cpu == that_cpu.
> >
> > Fixes: 518cd6234178 ("sched: Only queue remote wakeups when crossing cache boundaries")
> > Reported-by: Jing-Ting Wu <jing-ting.wu@mediatek.com>
> > Signed-off-by: Vincent Donnefort <vincent.donnefort@arm.com>
> > Reviewed-by: Valentin Schneider <valentin.schneider@arm.com>
> 
>  Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org>
> 
> >
> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > index f2611b9cf503..f5ca15cdcff4 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -3726,6 +3726,9 @@ void wake_up_if_idle(int cpu)
> >
> >  bool cpus_share_cache(int this_cpu, int that_cpu)
> >  {
> > +       if (this_cpu == that_cpu)
> > +               return true;
> > +
> >         return per_cpu(sd_llc_id, this_cpu) == per_cpu(sd_llc_id, that_cpu);
> >  }

Blergh, that's annoying. Thanks guys, picked it up for /urgent

  reply	other threads:[~2021-11-08 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 17:51 Vincent Donnefort
2021-11-05 15:08 ` Vincent Guittot
2021-11-08 11:19   ` Peter Zijlstra [this message]
2021-11-11 12:22 ` [tip: sched/urgent] " tip-bot2 for Vincent Donnefort
2021-11-15 10:46 ` [PATCH] " Shinichiro Kawasaki
2021-11-15 18:33   ` Valentin Schneider
2021-11-16  8:02     ` Vincent Guittot
2021-11-16  8:45       ` Shinichiro Kawasaki

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=YYkHu8kkp9q9/QPP@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Valentin.Schneider@arm.com \
    --cc=Vincent.Donnefort@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jing-ting.wu@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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

all inboxes | Powered by JetHome®