From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, James Dykman <jdykman@us.ibm.com>
Subject: Re: [1/1] powerpc/mm: Add memory barrier in __hugepte_alloc()
Date: Fri, 22 Jul 2016 15:50:41 +1000 (AEST) [thread overview]
Message-ID: <3rwfrd6Vq2z9sxb@ozlabs.org> (raw)
In-Reply-To: <20160405190547.GA12673@us.ibm.com>
On Tue, 2016-05-04 at 19:05:47 UTC, Sukadev Bhattiprolu wrote:
> >From f7b73c6b4508fe9b141a43d92be2f9dd7d3c4a58 Mon Sep 17 00:00:00 2001
> From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> Date: Thu, 24 Mar 2016 02:07:57 -0400
> Subject: [PATCH 1/1] powerpc/mm: Add memory barrier in __hugepte_alloc()
>
> __hugepte_alloc() uses kmem_cache_zalloc() to allocate a zeroed PTE
> and proceeds to use the newly allocated PTE. Add a memory barrier to
> make sure that the other CPUs see a properly initialized PTE.
>
> Based on a fix suggested by James Dykman.
>
> Reported-by: James Dykman <jdykman@us.ibm.com>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> Tested-by: James Dykman <jdykman@us.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/0eab46be21449f1612791201aa
cheers
prev parent reply other threads:[~2016-07-22 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 19:05 [PATCH 1/1] powerpc/mm: Add memory barrier in __hugepte_alloc() Sukadev Bhattiprolu
2016-04-06 9:56 ` Michal Hocko
2016-04-06 10:09 ` Aneesh Kumar K.V
2016-04-06 11:27 ` Michal Hocko
2016-07-22 5:50 ` Michael Ellerman [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=3rwfrd6Vq2z9sxb@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=jdykman@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sukadev@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).