From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linuxppc-dev@lists.ozlabs.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Christoph Lameter <cl@linux.com>,
Tiejun Chen <tiejun.chen@windriver.com>,
Scott Wood <scottwood@freescale.com>
Subject: Re: [PATCH] powerpc: mm: fixup preempt undefflow with huge pages
Date: Mon, 07 Mar 2016 21:04:05 +0530 [thread overview]
Message-ID: <877fheti8i.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160307135506.GA12595@linutronix.de>
Sebastian Andrzej Siewior <bigeasy@linutronix.de> writes:
> [ text/plain ]
> hugepd_free() used __get_cpu_var() once. Nothing ensured that the code
> accessing the variable did not migrate from one CPU to another and soon
> this was noticed by Tiejun Chen in 94b09d755462 ("powerpc/hugetlb:
> Replace __get_cpu_var with get_cpu_var"). So we had it fixed.
>
> Christoph Lameter was doing his __get_cpu_var() replaces and forgot
> PowerPC. Then he noticed this and sent his fixed up batch again which
> got applied as 69111bac42f5 ("powerpc: Replace __get_cpu_var uses").
>
> The careful reader will noticed one little detail: get_cpu_var() got
> replaced with this_cpu_ptr(). So now we have a put_cpu_var() which does
> a preempt_enable() and nothing that does preempt_disable() so we
> underflow the preempt counter.
>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: Christoph Lameter <cl@linux.com>
> Cc: Michael Ellerman <mpe@ellerman.id.au>
> Cc: Tiejun Chen <tiejun.chen@windriver.com>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> arch/powerpc/mm/hugetlbpage.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/mm/hugetlbpage.c b/arch/powerpc/mm/hugetlbpage.c
> index 744e24bcb85c..9e8919b39640 100644
> --- a/arch/powerpc/mm/hugetlbpage.c
> +++ b/arch/powerpc/mm/hugetlbpage.c
> @@ -414,7 +414,7 @@ static void hugepd_free(struct mmu_gather *tlb, void *hugepte)
> {
> struct hugepd_freelist **batchp;
>
> - batchp = this_cpu_ptr(&hugepd_freelist_cur);
> + batchp = get_cpu_ptr(&hugepd_freelist_cur);
>
> if (atomic_read(&tlb->mm->mm_users) < 2 ||
> cpumask_equal(mm_cpumask(tlb->mm),
IMHO it would better if we do
batchp = get_cpu_var(hugepd_freelist_cpu);
so that it match the existing
put_cpu_var(hugepd_freelist_cur);
While you are there, can you also fix the wrong indentation on line 423
?
-aneesh
next prev parent reply other threads:[~2016-03-07 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 13:55 [PATCH] powerpc: mm: fixup preempt undefflow with huge pages Sebastian Andrzej Siewior
2016-03-07 15:34 ` Aneesh Kumar K.V [this message]
2016-03-07 23:41 ` Benjamin Herrenschmidt
2016-03-08 8:08 ` Sebastian Andrzej Siewior
2016-03-08 9:03 ` [PATCH v2] " Sebastian Andrzej Siewior
2016-03-09 19:34 ` Aneesh Kumar K.V
2016-03-29 13:40 ` Sebastian Andrzej Siewior
2016-03-30 0:41 ` Michael Ellerman
2016-03-30 8:17 ` Sebastian Andrzej Siewior
2016-03-30 23:29 ` [v2] " Michael Ellerman
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=877fheti8i.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bigeasy@linutronix.de \
--cc=cl@linux.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=tiejun.chen@windriver.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).