linux-kernel - Re: Possible regression: MSI vector leakage since 2.6.18-rc5ish (Unable to repeatedly allocate/free MSI interrupt)

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: <m1zm81ipqg.fsf@ebiederm.dsl.xmission.com>
Date:	Mon, 29 Jan 2007 12:42:47 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Auke Kok <auke-jan.h.kok@...el.com>,
	linux-pci maillist <linux-pci@...ey.karlin.mff.cuni.cz>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>,
	Linus Torvalds <torvalds@...l.org>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>
Subject: Re: Possible regression: MSI vector leakage since 2.6.18-rc5ish (Unable to repeatedly allocate/free MSI interrupt)

Linus Torvalds <torvalds@...ux-foundation.org> writes:

> On Mon, 29 Jan 2007, Auke Kok wrote:
>> 
>> Yes. A few hundred cycles of loading/unloading snd_hda_intel with enable_msi=1
>> didn't break it on i386.
>> 
>> I sure hope this can get into 2.6.20!
>
> Eric, can you write an explanation, add your sign-off, Auke's ACK, and 
> send out the result? The patch looked ok to me, but I do want the more 
> deeper explanation too (and sign-off, of course).

Sure.  Give me a couple of minutes.

Eric
-
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/