Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754113AbbERP2j (ORCPT ); Mon, 18 May 2015 11:28:39 -0400 Received: from terminus.zytor.com ([198.137.202.10]:45877 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753813AbbERP2b (ORCPT ); Mon, 18 May 2015 11:28:31 -0400 Date: Mon, 18 May 2015 08:27:31 -0700 From: tip-bot for NeilBrown Message-ID: Cc: rjw@rjwysocki.net, peterz@infradead.org, mingo@kernel.org, neil@brown.name, linux-kernel@vger.kernel.org, kalle.jokiniemi@jollamobile.com, tglx@linutronix.de, gta04-owner@goldelico.com, hpa@zytor.com, neilb@suse.de Reply-To: linux-kernel@vger.kernel.org, neil@brown.name, mingo@kernel.org, rjw@rjwysocki.net, peterz@infradead.org, tglx@linutronix.de, kalle.jokiniemi@jollamobile.com, gta04-owner@goldelico.com, neilb@suse.de, hpa@zytor.com In-Reply-To: <20150517151934.2393e8f8@notabene.brown> References: <20150517151934.2393e8f8@notabene.brown> To: linux-tip-commits@vger.kernel.org Subject: [tip:irq/core] genirq: Don' t suspend nested_thread irqs over system suspend Git-Commit-ID: 3c646f2c6aa9e918d7fc77867df7f430059f9ccc X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2302 Lines: 61 Commit-ID: 3c646f2c6aa9e918d7fc77867df7f430059f9ccc Gitweb: http://git.kernel.org/tip/3c646f2c6aa9e918d7fc77867df7f430059f9ccc Author: NeilBrown AuthorDate: Sun, 17 May 2015 15:19:34 +1000 Committer: Thomas Gleixner CommitDate: Mon, 18 May 2015 17:23:47 +0200 genirq: Don't suspend nested_thread irqs over system suspend Nested IRQs can only fire when the parent irq fires. So when the parent is suspended, there is no need to suspend the child irq. Suspending nested irqs can cause a problem is they are suspended or resumed in the wrong order. If an interrupt fires while the parent is active but the child is suspended, then the interrupt will not be acknowledged properly and so an interrupt storm can result. This is particularly likely if the parent is resumed before the child, and the interrupt was raised during suspend. Ensuring correct ordering would be possible, but it is simpler to just never suspend nested interrupts. Signed-off-by: NeilBrown Cc: GTA04 owners Cc: Kalle Jokiniemi Acked-by: Peter Zijlstra Cc: Rafael J. Wysocki Link: http://lkml.kernel.org/r/20150517151934.2393e8f8@notabene.brown Signed-off-by: Thomas Gleixner --- kernel/irq/pm.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/kernel/irq/pm.c b/kernel/irq/pm.c index 5204a6d..d22786a 100644 --- a/kernel/irq/pm.c +++ b/kernel/irq/pm.c @@ -123,6 +123,8 @@ void suspend_device_irqs(void) unsigned long flags; bool sync; + if (irq_settings_is_nested_thread(desc)) + continue; raw_spin_lock_irqsave(&desc->lock, flags); sync = suspend_device_irq(desc, irq); raw_spin_unlock_irqrestore(&desc->lock, flags); @@ -163,6 +165,8 @@ static void resume_irqs(bool want_early) if (!is_early && want_early) continue; + if (irq_settings_is_nested_thread(desc)) + continue; raw_spin_lock_irqsave(&desc->lock, flags); resume_irq(desc, irq); -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/