linux-kernel - RE: [PATCH] ARCH: 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 for Android: free password hash cracker in your pocket

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

Message-ID: <D5C1322C3E673F459512FB59E0DDC32904F9ED1F@orsmsx414.amr.corp.intel.com>
Date:	Mon, 28 Apr 2008 14:21:26 -0700
From:	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
To:	"Thomas Gleixner" <tglx@...utronix.de>
Cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"LKML" <linux-kernel@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	<netdev@...r.kernel.org>
Subject: RE: [PATCH] ARCH: Fix 32-bit x86 MSI-X allocation leakage

> Ok, that makes sense. I just did not get the context out of 
> your commit log. Adding the commit which caused the trouble 
> to the commit log makes it easier to understand. So the 
> problem is unrelated to the merger, it's caused by a patch 
> which was pending against the i386 tree around the time of 
> the merger and which was converted to the merge tree.

That's my miss for not including the specific context.  I will try to be
better about that in the future.  I do appreciate the interest though to
make sure it's specifically understood when this bug was introduced.

Cheers,

-PJ Waskiewicz
--
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/