From: Stefan Bader <stefan.bader@canonical.com>
To: stable@kernel.org
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: [PATCH] x86: Reserve FIRST_DEVICE_VECTOR in used_vectors bitmap
Date: Fri, 10 Oct 2008 16:01:54 -0400 [thread overview]
Message-ID: <48EFB4B2.2020508@canonical.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Affected: 2.6.24-2.6.27
Someone from the community found out, that after repeatedly unloading and
loading a device driver that uses MSI IRQs, the system eventually assigned
the vector initially reserved for IRQ0 to the device driver.
The reason for this is, that although IRQ0 is tied to the FIRST_DEVICE_VECTOR
when declaring the irq_vector table, the corresponding bit in the used_vectors
map is not set. So, if vectors are released and assigned often enough, the
vector will get assigned to another interrupt. This happens more often with
MSI interrupts as those are exclusively using a vector.
Fix this by setting the bit for the FIRST_DEVICE_VECTOR in the bitmap.
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
--
When all other means of communication fail, try words!
[-- Attachment #2: 0001-x86-Reserve-FIRST_DEVICE_VECTOR-in-used_vectors-bit.patch --]
[-- Type: application/mbox, Size: 1523 bytes --]
next reply other threads:[~2008-10-10 20:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 20:01 Stefan Bader [this message]
2008-10-10 20:16 ` [stable] [PATCH] x86: Reserve FIRST_DEVICE_VECTOR in used_vectors bitmap Greg KH
2008-10-10 20:23 ` Ingo Molnar
2008-10-10 20:29 ` Greg KH
2008-10-10 20:36 ` Stefan Bader
2008-10-10 20:41 ` Greg KH
2008-10-10 20:16 ` Greg KH
2008-10-10 20:22 ` Stefan Bader
2008-10-10 20:18 ` Greg KH
2008-10-10 20:24 ` Stefan Bader
2008-10-10 20:35 ` H. Peter Anvin
2008-10-10 20:41 ` Greg KH
2008-10-10 20:50 ` Alan Cox
2008-10-10 21:12 ` Greg KH
2008-10-10 21:49 ` Alan Cox
2008-10-10 22:09 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2008-09-29 13:39 Stefan Bader
2008-09-30 9:51 ` Ingo Molnar
2008-09-30 12:53 ` Stefan Bader
2008-10-02 12:14 ` Stefan Bader
2008-10-03 8:56 ` Ingo Molnar
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=48EFB4B2.2020508@canonical.com \
--to=stefan.bader@canonical.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox