From: songyuanzheng <songyuanzheng@huawei.com>
To: Dennis Zhou <dennis@kernel.org>, Christoph Lameter <cl@gentwo.de>
Cc: "tj@kernel.org" <tj@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH -next] mm/percpu: fix data-race with pcpu_nr_empty_pop_pages
Date: Wed, 27 Oct 2021 07:12:06 +0000 [thread overview]
Message-ID: <4be3bce19c1d44c4a04bb411dfa26182@huawei.com> (raw)
In-Reply-To: <YXdq7+PJqGLCu4nH@fedora>
Hello,
Thanks for the advice, Dennis Zhou and Christoph Lameter.
I really appreciate it.
I edited this patch by changing the pcpu_nr_empty_pop_pages to atomic_t variable.
Here is the v2 patch: https://patchwork.kernel.org/project/linux-mm/patch/20211026084312.2138852-1-songyuanzheng@huawei.com/.
Would you mind reviewing it again?
Thanks,
Yuanzheng Song
-----Original Message-----
From: Dennis Zhou [mailto:dennis@kernel.org]
Sent: Tuesday, October 26, 2021 10:42 AM
To: Christoph Lameter <cl@gentwo.de>
Cc: songyuanzheng <songyuanzheng@huawei.com>; dennis@kernel.org; tj@kernel.org; akpm@linux-foundation.org; linux-mm@kvack.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] mm/percpu: fix data-race with pcpu_nr_empty_pop_pages
Hello,
On Mon, Oct 25, 2021 at 09:50:48AM +0200, Christoph Lameter wrote:
> On Mon, 25 Oct 2021, Yuanzheng Song wrote:
>
> > When reading the pcpu_nr_empty_pop_pages in pcpu_alloc() and writing
> > the pcpu_nr_empty_pop_pages in
> > pcpu_update_empty_pages() at the same time, the data-race occurs.
>
> Looks like a use case for the atomic RMV instructions.
>
Yeah. I see 2 options. Switch the variable over to an atomic or we can move the read behind pcpu_lock. All the writes are already behind it othewise that would actually be problematic. In this particular case, reading a wrong # of empty pages isn't a big deal as eventually the background work will get scheduled.
Thanks,
Dennis
> > To fix this issue, use READ_ONCE() and WRITE_ONCE() to read and
> > write the pcpu_nr_empty_pop_pages.
>
> Never thought that READ_ONCE and WRITE_ONCE can fix races like this.
> Really?
>
> > diff --git a/mm/percpu.c b/mm/percpu.c index
> > 293009cc03ef..e8ef92e698ab 100644
> > --- a/mm/percpu.c
> > +++ b/mm/percpu.c
> > @@ -574,7 +574,9 @@ static void pcpu_isolate_chunk(struct pcpu_chunk
> > *chunk)
> >
> > if (!chunk->isolated) {
> > chunk->isolated = true;
> > - pcpu_nr_empty_pop_pages -= chunk->nr_empty_pop_pages;
> > + WRITE_ONCE(pcpu_nr_empty_pop_pages,
> > + READ_ONCE(pcpu_nr_empty_pop_pages) -
> > + chunk->nr_empty_pop_pages);
>
> atomic_sub()?
>
> > }
> > list_move(&chunk->list,
> > &pcpu_chunk_lists[pcpu_to_depopulate_slot]);
> > }
> > @@ -585,7 +587,9 @@ static void pcpu_reintegrate_chunk(struct
> > pcpu_chunk *chunk)
> >
> > if (chunk->isolated) {
> > chunk->isolated = false;
> > - pcpu_nr_empty_pop_pages += chunk->nr_empty_pop_pages;
> > + WRITE_ONCE(pcpu_nr_empty_pop_pages,
> > + READ_ONCE(pcpu_nr_empty_pop_pages) +
> > + chunk->nr_empty_pop_pages);
>
> atomic_add()?
>
prev parent reply other threads:[~2021-10-27 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 7:00 Yuanzheng Song
2021-10-25 7:50 ` Christoph Lameter
2021-10-26 2:41 ` Dennis Zhou
2021-10-27 7:12 ` songyuanzheng [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=4be3bce19c1d44c4a04bb411dfa26182@huawei.com \
--to=songyuanzheng@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.de \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.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®