* [PATCH] ARCH 2.6.24.y: Fix 32-bit x86 MSI-X allocation leakage
@ 2008-04-28 18:56 PJ Waskiewicz
0 siblings, 0 replies; 3+ messages in thread
From: PJ Waskiewicz @ 2008-04-28 18:56 UTC (permalink / raw)
To: stable, linux-kernel; +Cc: netdev
Resend now that this patch was merged into -upstream.
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>
---
arch/x86/kernel/io_apic_32.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/io_apic_32.c b/arch/x86/kernel/io_apic_32.c
index 232fdeb..9994c52 100644
--- a/arch/x86/kernel/io_apic_32.c
+++ b/arch/x86/kernel/io_apic_32.c
@@ -2478,6 +2478,7 @@ void destroy_irq(unsigned int irq)
dynamic_irq_cleanup(irq);
spin_lock_irqsave(&vector_lock, flags);
+ clear_bit(irq_vector[irq], used_vectors);
irq_vector[irq] = 0;
spin_unlock_irqrestore(&vector_lock, flags);
}
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] ARCH 2.6.24.y: Fix 32-bit x86 MSI-X allocation leakage
2008-04-26 0:59 PJ Waskiewicz
@ 2008-04-29 10:22 ` Ingo Molnar
0 siblings, 0 replies; 3+ messages in thread
From: Ingo Molnar @ 2008-04-29 10:22 UTC (permalink / raw)
To: PJ Waskiewicz; +Cc: stable, linux-kernel, netdev
* 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PATCH] ARCH 2.6.24.y: Fix 32-bit x86 MSI-X allocation leakage
@ 2008-04-26 0:59 PJ Waskiewicz
2008-04-29 10:22 ` Ingo Molnar
0 siblings, 1 reply; 3+ messages in thread
From: PJ Waskiewicz @ 2008-04-26 0:59 UTC (permalink / raw)
To: stable, linux-kernel; +Cc: netdev
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>
---
arch/x86/kernel/io_apic_32.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/io_apic_32.c b/arch/x86/kernel/io_apic_32.c
index 232fdeb..9994c52 100644
--- a/arch/x86/kernel/io_apic_32.c
+++ b/arch/x86/kernel/io_apic_32.c
@@ -2478,6 +2478,7 @@ void destroy_irq(unsigned int irq)
dynamic_irq_cleanup(irq);
spin_lock_irqsave(&vector_lock, flags);
+ clear_bit(irq_vector[irq], used_vectors);
irq_vector[irq] = 0;
spin_unlock_irqrestore(&vector_lock, flags);
}
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-04-29 10:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-04-28 18:56 [PATCH] ARCH 2.6.24.y: Fix 32-bit x86 MSI-X allocation leakage PJ Waskiewicz
-- strict thread matches above, loose matches on Subject: below --
2008-04-26 0:59 PJ Waskiewicz
2008-04-29 10:22 ` Ingo Molnar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®