lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Aug 2021 19:16:19 +0200 From: Thomas Gleixner <tglx@...utronix.de> To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Valentin Schneider <valentin.schneider@....com> Cc: linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org, Will Deacon <will@...nel.org>, Mark Rutland <mark.rutland@....com>, Marc Zyngier <maz@...nel.org>, Mel Gorman <mgorman@...hsingularity.net> Subject: Re: [SPLAT 1/3] arm_pmu: Sleeping spinlocks down armpmu_alloc_atomic() On Tue, Aug 10 2021 at 15:54, Sebastian Andrzej Siewior wrote: > On 2021-08-10 14:41:25 [+0100], Valentin Schneider wrote: >> [ 4.172817] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:35 > > Would it work to allocate the memory upfront and invoke the HP callback > via smp_function_call()? Huch? If the memory is allocated during the prepare stage then the actual hotplug callback can just use it. So what's the SMP function call for? Thanks, tglx
Powered by blists - more mailing lists