netdev - Re: [PATCH] e1000: Fix msi enable leak on error, don't print error message, cleanup

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: <464B5734.2070904@hp.com>
Date:	Wed, 16 May 2007 12:10:44 -0700
From:	Rick Jones <rick.jones2@...com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Jeff Garzik <jeff@...zik.org>, Auke Kok <auke-jan.h.kok@...el.com>,
	netdev@...r.kernel.org, e1000-devel@...ts.sourceforge.net
Subject: Re: [PATCH] e1000: Fix msi enable leak on error, don't print error
 message,	cleanup

H. Peter Anvin wrote:
> Rick Jones wrote:
> 
>>Some more of my paranoid questions :)
>>
>>So, if a driver tries to enable MSI and that is unsuccessful (I'll try
>>to avoid using the possibly loaded term "fails") shouldn't that show-up
>>_somewhere_?
> 
> 
> It already does -- in /proc/interrupts.

But that is rather incidental isn't it?  Would some sort of system health 
monitor be likely to be checking that for interrupt flavors?  And just looking 
at /proc/interrupts, while it tells you what sort of interrupt is being used, it 
doesn't (IIRC) say anything about what sort of interrupt the driver _tried_ to use.

rick jones
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html