From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Mel Gorman <mgorman@techsingularity.net>
Subject: [SPLAT 1/3] arm_pmu: Sleeping spinlocks down armpmu_alloc_atomic()
Date: Tue, 10 Aug 2021 14:41:25 +0100 [thread overview]
Message-ID: <20210810134127.1394269-2-valentin.schneider@arm.com> (raw)
In-Reply-To: <20210810134127.1394269-1-valentin.schneider@arm.com>
[ 4.172817] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:35
[ 4.172820] in_atomic(): 0, irqs_disabled(): 128, non_block: 0, pid: 19, name: cpuhp/0
[ 4.172822] 3 locks held by cpuhp/0/19:
[ 4.172824] #0: ffff800011cf8690 (cpu_hotplug_lock){++++}-{0:0}, at: cpuhp_thread_fun (kernel/cpu.c:739)
[ 4.172833] #1: ffff800011cf86e0 (cpuhp_state-up){+.+.}-{0:0}, at: cpuhp_thread_fun (kernel/cpu.c:739)
[ 4.172838] #2: ffff008f36237c08 (&(&c->lock)->lock){+.+.}-{0:0}, at: ___slab_alloc (mm/slub.c:2872)
[ 4.172844] irq event stamp: 40
[ 4.172845] hardirqs last enabled at (39): finish_task_switch (./arch/arm64/include/asm/irqflags.h:35 kernel/sched/sched.h:1319 kernel/sched/core.c:4531 kernel/sched/core.c:4649)
[ 4.172849] hardirqs last disabled at (40): cpuhp_thread_fun (kernel/cpu.c:761 (discriminator 1))
[ 4.172851] softirqs last enabled at (0): copy_process (./include/linux/lockdep.h:195 ./include/linux/lockdep.h:202 ./include/linux/lockdep.h:208 ./include/linux/seqlock.h:78 kernel/fork.c:2084)
[ 4.172855] softirqs last disabled at (0): 0x0
[ 4.172860] CPU: 0 PID: 19 Comm: cpuhp/0 Tainted: G W 5.14.0-rc4-rt6-torture+ #56
[ 4.172863] Hardware name: MiTAC RAPTOR EV-883832-X3-0001/RAPTOR, BIOS 1.0 06/28/2019
[ 4.172864] Call trace:
[ 4.172865] dump_backtrace (arch/arm64/kernel/stacktrace.c:151)
[ 4.172867] show_stack (arch/arm64/kernel/stacktrace.c:217)
[ 4.172869] dump_stack_lvl (lib/dump_stack.c:106)
[ 4.172872] dump_stack (lib/dump_stack.c:113)
[ 4.172874] ___might_sleep (kernel/sched/core.c:9306)
[ 4.172877] rt_spin_lock (kernel/locking/rtmutex.c:1641 (discriminator 4) kernel/locking/spinlock_rt.c:30 (discriminator 4) kernel/locking/spinlock_rt.c:36 (discriminator 4) kernel/locking/spinlock_rt.c:44 (discriminator 4))
[ 4.172879] ___slab_alloc (mm/slub.c:2872)
[ 4.172882] __slab_alloc.isra.0 (mm/slub.c:3038)
[ 4.172884] kmem_cache_alloc_trace (mm/slub.c:3129 mm/slub.c:3171 mm/slub.c:3188)
[ 4.172886] __armpmu_alloc (./include/linux/slab.h:591 ./include/linux/slab.h:721 drivers/perf/arm_pmu.c:869)
[ 4.172889] armpmu_alloc_atomic (drivers/perf/arm_pmu.c:927)
[ 4.172891] arm_pmu_acpi_cpu_starting (drivers/perf/arm_pmu_acpi.c:202 drivers/perf/arm_pmu_acpi.c:264)
[ 4.172893] cpuhp_invoke_callback (kernel/cpu.c:180)
[ 4.172895] cpuhp_thread_fun (kernel/cpu.c:762 (discriminator 3))
[ 4.172896] smpboot_thread_fn (kernel/smpboot.c:164 (discriminator 3))
[ 4.172900] kthread (kernel/kthread.c:327)
[ 4.172902] ret_from_fork (arch/arm64/kernel/entry.S:783)
next prev parent reply other threads:[~2021-08-10 13:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 13:41 [SPLAT 0/3] Sleeping spinlocks in troublesome contexts on v5.14-rc4-rt6 Valentin Schneider
2021-08-10 13:41 ` Valentin Schneider [this message]
2021-08-10 13:54 ` [SPLAT 1/3] arm_pmu: Sleeping spinlocks down armpmu_alloc_atomic() Sebastian Andrzej Siewior
2021-08-10 17:16 ` Thomas Gleixner
2021-08-10 18:39 ` Sebastian Andrzej Siewior
2021-08-10 19:56 ` Thomas Gleixner
2021-08-10 13:41 ` [SPLAT 2/3] irqchip/gic-v3-its: Sleeping spinlocks down gic_reserve_range() Valentin Schneider
2021-08-11 8:50 ` Marc Zyngier
2021-08-11 12:28 ` Thomas Gleixner
2021-08-11 15:14 ` Marc Zyngier
2021-08-17 15:16 ` Ard Biesheuvel
2021-08-10 13:41 ` [SPLAT 3/3] gpio: dwapb: Sleeping spinlocks down IRQ mapping Valentin Schneider
2021-08-10 20:33 ` Thomas Gleixner
2021-08-11 10:52 ` Andy Shevchenko
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=20210810134127.1394269-2-valentin.schneider@arm.com \
--to=valentin.schneider@arm.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=tglx@linutronix.de \
--cc=will@kernel.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
all inboxes | Powered by JetHome®