From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: npiggin@gmail.com
Subject: Re: powerpc/64e: Fix oops due to deferral of paca allocation
Date: Sun, 1 Apr 2018 01:04:16 +1100 (AEDT) [thread overview]
Message-ID: <40D0bQ264Xz9s3x@ozlabs.org> (raw)
In-Reply-To: <20180331115138.5731-1-mpe@ellerman.id.au>
On Sat, 2018-03-31 at 11:51:38 UTC, Michael Ellerman wrote:
> On 64-bit Book3E systems, in setup_tlb_core_data() we reference other
> CPUs pacas. But in commit 59f577743d71 ("powerpc/64: Defer paca
> allocation until memory topology is discovered") the allocation of
> non-boot-CPU pacas was deferred until later in boot.
>
> This leads to an oops:
>
> CPU maps initialized for 1 thread per core
> Unable to handle kernel paging request for data at address 0x8888888888888918
> Faulting instruction address: 0xc000000000e2f0d0
> Oops: Kernel access of bad area, sig: 11 [#1]
> NIP .setup_tlb_core_data+0xdc/0x160
> Call Trace:
> .setup_tlb_core_data+0x5c/0x160 (unreliable)
> .setup_arch+0x80/0x348
> .start_kernel+0x7c/0x598
> start_here_common+0x1c/0x40
>
> Luckily setup_tlb_core_data() is called immediately prior to
> smp_setup_pacas(). So simply switching their order is sufficient to
> fix the oops and seems unlikely to have any other unwanted side
> effects.
>
> Fixes: 59f577743d71 ("powerpc/64: Defer paca allocation until memory topology is discovered")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Applied to powerpc next.
https://git.kernel.org/powerpc/c/1d0afc0d5a7c281f8ced3bd39f61f3
cheers
prev parent reply other threads:[~2018-03-31 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 11:51 [PATCH] powerpc/64e: Fix oops due to deferral of paca allocation Michael Ellerman
2018-03-31 14:04 ` 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=40D0bQ264Xz9s3x@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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).