linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shakeel Butt <shakeelb@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH v2] percpu_counter: add percpu_counter_sum_all interface
Date: Tue, 8 Nov 2022 17:29:31 -0800	[thread overview]
Message-ID: <CALvZod7XREiFFgqb8KAMOzpPjozsu90p9Oz+tAVuBPGVs4=mvA@mail.gmail.com> (raw)
In-Reply-To: <20221108172603.8d547faa8f0cf0c340fd7150@linux-foundation.org>

On Tue, Nov 8, 2022 at 5:26 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Wed,  9 Nov 2022 01:20:11 +0000 Shakeel Butt <shakeelb@google.com> wrote:
>
> > However there is a small race window between the online CPUs traversal
> > of percpu_counter_sum and the CPU offline callback. The offline callback
> > has to traverse all the percpu_counters on the system to flush the CPU
> > local data which can be a lot. During that time, the CPU which is going
> > offline has already been published as offline to all the readers. So, as
> > the offline callback is running, percpu_counter_sum can be called for
> > one counter which has some state on the CPU going offline. Since
> > percpu_counter_sum only traverses online CPUs, it will skip that
> > specific CPU and the offline callback might not have flushed the state
> > for that specific percpu_counter on that offlined CPU.
>
> LGTM.
>
> What are the user-visible effects of this bug?  Should we cc:stable?  If
> so, can you identify a suitable Fixes:?
>

The patch which exposed this is still in mm-unstable (converting rss
stats in mm_struct into percpu_counter) and other percpu_counter users
don't really need this new interface. So, there is no need for a
cc:stable.

thanks,
Shakeel


      reply	other threads:[~2022-11-09  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  1:20 Shakeel Butt
2022-11-09  1:26 ` Andrew Morton
2022-11-09  1:29   ` Shakeel Butt [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='CALvZod7XREiFFgqb8KAMOzpPjozsu90p9Oz+tAVuBPGVs4=mvA@mail.gmail.com' \
    --to=shakeelb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.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