From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752606AbcAGOfw (ORCPT ); Thu, 7 Jan 2016 09:35:52 -0500 Received: from foss.arm.com ([217.140.101.70]:40126 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752160AbcAGOfv (ORCPT ); Thu, 7 Jan 2016 09:35:51 -0500 Message-ID: <568E77C2.9060002@arm.com> Date: Thu, 07 Jan 2016 14:35:46 +0000 From: Marc Zyngier Organization: ARM Ltd User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: Daniel Thompson , Thomas Gleixner , Jason Cooper , Russell King CC: Will Deacon , Catalin Marinas , Stephen Boyd , John Stultz , Steven Rostedt , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, patches@linaro.org, linaro-kernel@lists.linaro.org, Sumit Semwal , Dirk Behme , Daniel Drake , Dmitry Pervushin , Tim Sander , Petr Mladek Subject: Re: [PATCH 4.4-rc5 v22 2/4] irqchip: gic: Make gic_raise_softirq FIQ-safe References: <1450644757-18734-1-git-send-email-daniel.thompson@linaro.org> <1450644757-18734-3-git-send-email-daniel.thompson@linaro.org> In-Reply-To: <1450644757-18734-3-git-send-email-daniel.thompson@linaro.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/12/15 20:52, Daniel Thompson wrote: > It is currently possible for FIQ handlers to re-enter gic_raise_softirq() > and lock up. > > gic_raise_softirq() > lock(x); > -~-> FIQ > handle_fiq() > gic_raise_softirq() > lock(x); <-- Lockup > > arch/arm/ uses IPIs to implement arch_irq_work_raise(), thus this issue > renders it difficult for FIQ handlers to safely defer work to less > restrictive calling contexts. > > This patch fixes the problem by converting the cpu_map_migration_lock > into a rwlock making it safe to re-enter the function. > > Note that having made it safe to re-enter gic_raise_softirq() we no > longer need to mask interrupts during gic_raise_softirq() because the > b.L migration is always performed from task context. > > Signed-off-by: Daniel Thompson > Cc: Thomas Gleixner > Cc: Jason Cooper > Cc: Russell King > Cc: Marc Zyngier > Acked-by: Nicolas Pitre Acked-by: Marc Zyngier M. -- Jazz is not dead. It just smells funny... From mboxrd@z Thu Jan 1 00:00:00 1970 From: marc.zyngier@arm.com (Marc Zyngier) Date: Thu, 07 Jan 2016 14:35:46 +0000 Subject: [PATCH 4.4-rc5 v22 2/4] irqchip: gic: Make gic_raise_softirq FIQ-safe In-Reply-To: <1450644757-18734-3-git-send-email-daniel.thompson@linaro.org> References: <1450644757-18734-1-git-send-email-daniel.thompson@linaro.org> <1450644757-18734-3-git-send-email-daniel.thompson@linaro.org> Message-ID: <568E77C2.9060002@arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 20/12/15 20:52, Daniel Thompson wrote: > It is currently possible for FIQ handlers to re-enter gic_raise_softirq() > and lock up. > > gic_raise_softirq() > lock(x); > -~-> FIQ > handle_fiq() > gic_raise_softirq() > lock(x); <-- Lockup > > arch/arm/ uses IPIs to implement arch_irq_work_raise(), thus this issue > renders it difficult for FIQ handlers to safely defer work to less > restrictive calling contexts. > > This patch fixes the problem by converting the cpu_map_migration_lock > into a rwlock making it safe to re-enter the function. > > Note that having made it safe to re-enter gic_raise_softirq() we no > longer need to mask interrupts during gic_raise_softirq() because the > b.L migration is always performed from task context. > > Signed-off-by: Daniel Thompson > Cc: Thomas Gleixner > Cc: Jason Cooper > Cc: Russell King > Cc: Marc Zyngier > Acked-by: Nicolas Pitre Acked-by: Marc Zyngier M. -- Jazz is not dead. It just smells funny...