From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] perf: arm_pmu_acpi: Fix armpmu_alloc call from invalid context
Date: Mon, 26 Feb 2018 13:05:36 +0000 [thread overview]
Message-ID: <20180226130535.7wvvyst5bwj76ss3@salmiak> (raw)
In-Reply-To: <1518112700.2911.0.camel@redhat.com>
On Thu, Feb 08, 2018 at 12:58:20PM -0500, Mark Salter wrote:
> On Thu, 2018-02-08 at 17:54 +0000, Mark Rutland wrote:
> > Hi Mark,
> >
> > On Thu, Feb 08, 2018 at 12:45:04PM -0500, Mark Salter wrote:
> > > When booting an arm64 debug kernel with ACPI, I see:
> > >
> > > BUG: sleeping function called from invalid context at mm/slab.h:420
> > > in_atomic(): 0, irqs_disabled(): 128, pid: 12, name: cpuhp/0
> > > 1 lock held by cpuhp/0/12:
> > > #0: (cpuhp_state-up){+.+.}, at: [<0000000057aa0dae>] cpuhp_thread_fun+0x13c/0x258
> > > irq event stamp: 28
> > > hardirqs last enabled at (27): [<000000000b861658>] _raw_spin_unlock_irq+0x38/0x58
> > > hardirqs last disabled at (28): [<000000006231cfb1>] cpuhp_thread_fun+0xd0/0x258
> > > softirqs last enabled at (0): [<0000000054d9737a>] copy_process.isra.32.part.33+0x450/0x1480
> > > softirqs last disabled at (0): [< (null)>] (null)
> > > CPU: 0 PID: 12 Comm: cpuhp/0 Not tainted 4.15.0+ #18
> > > Hardware name: AppliedMicro X-Gene Mustang Board/X-Gene Mustang Board, BIOS 3.06.25 Oct 17 2016
> > > Call trace:
> > > dump_backtrace+0x0/0x188
> > > show_stack+0x24/0x2c
> > > dump_stack+0xa4/0xe0
> > > ___might_sleep+0x208/0x234
> > > __might_sleep+0x58/0x8c
> > > kmem_cache_alloc_trace+0x248/0x3e0
> > > armpmu_alloc+0x38/0x1a8
> > > arm_pmu_acpi_cpu_starting+0x11c/0x15c
> > > cpuhp_invoke_callback+0x120/0x100c
> > > cpuhp_thread_fun+0xe8/0x258
> > > smpboot_thread_fn+0x170/0x268
> > > kthread+0x110/0x13c
> > > ret_from_fork+0x10/0x18
> >
> > I have patches to address this:
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2018-February/557838.html
> > https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/log/?h=arm64/acpi-pmu-lockdep
>
> Awesome, I completely missed that. Thanks.
As a heads-up, these were merged in v4.16-rc3.
Mark.
prev parent reply other threads:[~2018-02-26 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 17:45 [PATCH] perf: arm_pmu_acpi: Fix armpmu_alloc call from invalid context Mark Salter
2018-02-08 17:54 ` Mark Rutland
2018-02-08 17:58 ` Mark Salter
2018-02-26 13:05 ` Mark Rutland [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=20180226130535.7wvvyst5bwj76ss3@salmiak \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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