| 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
| ||
|
Date: Thu, 7 Aug 2008 09:03:22 -0700 From: Jesse Barnes <jbarnes@...tuousgeek.org> To: James Bottomley <James.Bottomley@...senpartnership.com>, greg@...ah.com Cc: linux-scsi <linux-scsi@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org Subject: Re: [PATCH 1/2] pci: add misrouted interrupt error handling On Tuesday, August 5, 2008 2:54 pm James Bottomley wrote: > > or somesuch. That seems just as simple for driver writers as your > > initial patch, and the function is named in accordance with what it > > actually does, rather than what it's used for... > > It could, but if the bridge is the culprit (as it usually is for MSI > problems), this print won't help identify it. > > Therefore, rather than give driver writers a recipe for "print this and > this and go to the bridge and print this", I'd rather have a single PCI > callback that prints all the (hopefully) relevant information that will > allow either fixing or blacklisting. So in addition to the IRQ type check we need to dump some device topology information... yeah that makes sense. I wonder if the driver core should provide something like this. Greg? In the meantime we can definitely add the IRQ type function. Thanks, Jesse -- 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/
Powered by blists - more mailing lists