linux-kernel - Re: [stable] [PATCH] ARCH 2.6.24.y: Fix 32-bit x86 MSI-X allocation leakage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080429220115.GE2302@elte.hu>
Date:	Wed, 30 Apr 2008 00:01:15 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Greg KH <greg@...ah.com>
Cc:	PJ Waskiewicz <peter.p.waskiewicz.jr@...el.com>,
	netdev@...r.kernel.org, stable@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [stable] [PATCH] ARCH 2.6.24.y: Fix 32-bit x86 MSI-X
	allocation leakage


* Greg KH <greg@...ah.com> wrote:

> On Tue, Apr 29, 2008 at 12:22:35PM +0200, Ingo Molnar wrote:
> > 
> > * PJ Waskiewicz <peter.p.waskiewicz.jr@...el.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.
> 
> What should I fix the commit message to be?  I copied the same commit 
> message that went into Linus's tree.  We should be consistent :)

instead of:

   This bug was introduced in the 2.6.24 i386/x86_64 tree merge,

use:

   This bug was introduced in the 2.6.24 lguest merge,

or just:

   This bug was introduced in 2.6.24,

:-)

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/