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/mm/64s: Fix preempt warning in slb_allocate_kernel()
Date: Tue, 13 Nov 2018 23:16:06 +1100 (AEDT) [thread overview]
Message-ID: <42vRRr3c9Gz9sCQ@ozlabs.org> (raw)
In-Reply-To: <20181101052105.17973-1-mpe@ellerman.id.au>
On Thu, 2018-11-01 at 05:21:05 UTC, Michael Ellerman wrote:
> With preempt enabled we see warnings in do_slb_fault():
>
> BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u33:0/98
> futex hash table entries: 4096 (order: 3, 524288 bytes)
> caller is do_slb_fault+0x204/0x230
> CPU: 5 PID: 98 Comm: kworker/u33:0 Not tainted 4.19.0-rc3-gcc-7.3.1-00022-g1936f094e164 #138
> Call Trace:
> dump_stack+0xb4/0x104 (unreliable)
> check_preemption_disabled+0x148/0x150
> do_slb_fault+0x204/0x230
> data_access_slb_common+0x138/0x180
>
> This is caused by the get_paca() in slb_allocate_kernel(), which
> includes a call to debug_smp_processor_id().
>
> slb_allocate_kernel() can only be called from do_slb_fault(), and in
> that path interrupts are hard disabled and so we can't be preempted,
> but we can't update the preempt flags (in thread_info) because that
> could cause an SLB fault.
>
> So just use local_paca which is safe and doesn't cause the warning.
>
> Fixes: 48e7b7695745 ("powerpc/64s/hash: Convert SLB miss handlers to C")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Applied to powerpc fixes.
https://git.kernel.org/powerpc/c/c8b00bb742dd036388f37d019dbb9d
cheers
prev parent reply other threads:[~2018-11-13 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 5:21 [PATCH] powerpc/mm/64s: Fix preempt warning in slb_allocate_kernel() Michael Ellerman
2018-11-13 12:16 ` 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=42vRRr3c9Gz9sCQ@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).