netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [stable] [PATCH] ARCH 2.6.25.y: Fix 32-bit x86 MSI-X allocation leakage
Date: Mon, 28 Apr 2008 10:38:02 -0700	[thread overview]
Message-ID: <20080428173801.GA933@kroah.com> (raw)
In-Reply-To: <20080426010025.7212.3940.stgit@scrappy.jf.intel.com>

On Fri, Apr 25, 2008 at 06:00:26PM -0700, PJ Waskiewicz 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.
> 
> This can be seen easily using the ixgbe 10 GbE driver on multi-core
> systems by simply loading and unloading the driver a few times.
> Depending on the number of available vectors on the host system, the
> MSI-X allocation will eventually fail, and the driver will only be
> able to use legacy interrupts.
> 
> Signed-off-by: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
> ---

When sending patches to -stable, please add "CC: stable
<stable@kernel.org> to the patch itself in the signed-off-by area, that
way we get notified automatically when it goes into Linus's tree so that
we can then know to apply it to the tree.  Otherwise it's a tough job to
try to track all of these knowing when to watch out for them to be
committed.

Can you please resend them to stable@kernel.org when they do go into
Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2008-04-28 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26  1:00 [PATCH] ARCH 2.6.25.y: Fix 32-bit x86 MSI-X allocation leakage PJ Waskiewicz
2008-04-28 17:38 ` Greg KH [this message]
2008-04-28 17:39   ` [stable] [PATCH] ARCH 2.6.25.y: Fix 32-bit x86 MSI-Xallocation leakage Waskiewicz Jr, Peter P

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=20080428173801.GA933@kroah.com \
    --to=greg@kroah.com \
    --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).