[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1236006812.5330.632.camel@laptop>
Date: Mon, 02 Mar 2009 16:13:32 +0100
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: David Brownell <david-b@...bell.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>, me@...ipebalbi.com,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
felipe.balbi@...ia.com, dmitry.torokhov@...il.com,
sameo@...nedhand.com, tglx@...utronix.de,
Ingo Molnar <mingo@...e.hu>
Subject: [PATCH] genirq: assert that irq handlers are indeed run in hardirq
context.
On Fri, 2009-02-27 at 15:18 -0800, David Brownell wrote:
> But these handlers are *NOT* running in hardirq context;
Ah, let us stop this tinkering dead in its tracks
Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
---
kernel/irq/handle.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
index c87d146..b75d73b 100644
--- a/kernel/irq/handle.c
+++ b/kernel/irq/handle.c
@@ -354,6 +354,8 @@ irqreturn_t handle_IRQ_event(unsigned int irq, struct irqaction *action)
irqreturn_t ret, retval = IRQ_NONE;
unsigned int status = 0;
+ BUG_ON(!in_irq());
+
if (!(action->flags & IRQF_DISABLED))
local_irq_enable_in_hardirq();
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists