From: Ingo Molnar <mingo@elte.hu>
To: PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ARCH 2.6.24.y: Fix 32-bit x86 MSI-X allocation leakage
Date: Tue, 29 Apr 2008 12:22:35 +0200 [thread overview]
Message-ID: <20080429102235.GI23198@elte.hu> (raw)
In-Reply-To: <20080426005950.7155.44626.stgit@scrappy.jf.intel.com>
* PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com> wrote:
> This bug was introduced in the 2.6.24 i386/x86_64 tree merge, where
> MSI-X vector allocation will eventually fail. The cause is the new
> bit array tracking used vectors is not getting cleared properly on IRQ
> destruction on the 32-bit APIC code.
Greg, please fix the commit message - this is a separate bug that has
nothing to do with the unification.
Ingo
next prev parent reply other threads:[~2008-04-29 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 0:59 [PATCH] ARCH 2.6.24.y: Fix 32-bit x86 MSI-X allocation leakage PJ Waskiewicz
2008-04-29 10:22 ` Ingo Molnar [this message]
2008-04-29 16:47 ` [stable] " Greg KH
2008-04-29 22:01 ` Ingo Molnar
2008-04-30 17:15 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2008-04-28 18:56 PJ Waskiewicz
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=20080429102235.GI23198@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).