From: David Brownell <david-b@pacbell.net>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: tglx@linutronix.de, mingo@redhat.com
Subject: [patch 2.6.18] genirq: remove oops with fasteoi irq_chip descriptors
Date: Fri, 22 Sep 2006 06:43:07 -0700 [thread overview]
Message-ID: <200609220643.07750.david-b@pacbell.net> (raw)
In-Reply-To: <200609220641.58938.david-b@pacbell.net>
The irq handler code can oops when used with an irq_chip with just
enable/disable/eoi methods, appropriate for handle_fasteoi_irq(),
either by (a) uninstalling, or (b) using it with a chained handler.
The problem was that the original code expected there would always
be mask/unmask/ack methods, and the fix is to instead use methods
which are always present and which more closely correspond to the
flag manipulation being done.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
--- d26.rc4test.orig/kernel/irq/chip.c 2006-09-21 16:41:11.000000000 -0700
+++ d26.rc4test/kernel/irq/chip.c 2006-09-21 18:04:07.000000000 -0700
@@ -482,10 +482,8 @@ __set_irq_handler(unsigned int irq,
/* Uninstall? */
if (handle == handle_bad_irq) {
- if (desc->chip != &no_irq_chip) {
- desc->chip->mask(irq);
- desc->chip->ack(irq);
- }
+ if (desc->chip != &no_irq_chip)
+ desc->chip->shutdown(irq);
desc->status |= IRQ_DISABLED;
desc->depth = 1;
}
@@ -495,7 +493,7 @@ __set_irq_handler(unsigned int irq,
desc->status &= ~IRQ_DISABLED;
desc->status |= IRQ_NOREQUEST | IRQ_NOPROBE;
desc->depth = 0;
- desc->chip->unmask(irq);
+ desc->chip->startup(irq);
}
spin_unlock_irqrestore(&desc->lock, flags);
}
next parent reply other threads:[~2006-09-27 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609220641.58938.david-b@pacbell.net>
2006-09-22 13:43 ` David Brownell [this message]
2006-09-27 21:38 ` [patch 2.6.18] genirq: remove oops with fasteoi irq_chip descriptors Thomas Gleixner
2006-09-27 23:21 ` David Brownell
2006-09-27 23:54 ` Thomas Gleixner
2006-09-28 0:39 ` [Bulk] " David Brownell
2006-09-28 1:18 ` Thomas Gleixner
2006-09-28 1:40 ` [Bulk] " David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609220643.07750.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.