[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b004e1f2-0b9e-a75c-4f6e-1daa2f0e7eed@gmail.com>
Date: Thu, 21 Feb 2019 13:02:54 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Marc Zyngier <marc.zyngier@....com>,
Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org, Doug Berger <opendmb@...il.com>,
Kevin Cernekee <cernekee@...il.com>,
Jason Cooper <jason@...edaemon.net>,
Brian Norris <computersforpeace@...il.com>,
Gregory Fong <gregory.0xf0@...il.com>,
"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@...adcom.com>,
"open list:BROADCOM BMIPS MIPS ARCHITECTURE"
<linux-mips@...r.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] irqchip: brcmstb-l2: use _irqsave variants in
non-interrupt code
On 2/21/19 2:15 AM, Marc Zyngier wrote:
> On Wed, 20 Feb 2019 14:15:28 -0800
> Florian Fainelli <f.fainelli@...il.com> wrote:
>
>> From: Doug Berger <opendmb@...il.com>
>>
>> Using the irq_gc_lock/irq_gc_unlock functions in the suspend and
>> resume functions creates the opportunity for a deadlock during
>> suspend, resume, and shutdown. Using the irq_gc_lock_irqsave/
>> irq_gc_unlock_irqrestore variants prevents this possible deadlock.
>>
>> Signed-off-by: Doug Berger <opendmb@...il.com>
>> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
>
> Applied to irqchip-next with:
>
> Cc: stable@...r.kernel.org
> Fixes: 7f646e92766e2 ("irqchip: brcmstb-l2: Add Broadcom Set Top Box
> Level-2 interrupt controller")
>
> Now, I'm worried this is not the only issue, see below.
Thanks for adding the Fixes tag, I should have done that, but did not
consider it to be a particularly serious issue (we have not see it in
real life, just only when LOCKDEP is enabled).
--
Florian
Powered by blists - more mailing lists