| 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: Fri, 09 Mar 2007 12:24:40 -0500 From: Chuck Ebbert <cebbert@...hat.com> To: "Eric W. Biederman" <ebiederm@...ssion.com> CC: linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: "No handler for vector" patches don't work on some systems Eric W. Biederman wrote: > Chuck Ebbert <cebbert@...hat.com> writes: >> >> So far I've tried the simple "survive having no handler >> for a vector" patch and the preliminary 3-patch series >> that was in -mm for a while, and neither work on the >> Dell PowerEdge 29xx and 19xx systems. These servers >> have the Intel 5000X chipset with the 6700PXH PCI Hub >> with dual independent PCI-X busses, each with its own >> I/OxAPIC with 24 interrupts. The fixes do work on >> "simple" systems but not on these high-end ones. > > > I would very much like to know if what I merged linus's tree helps. > It is a little more conservative, than my earlier patches. I need > a way to reproduce this or to work closely with someone who is, because > this sounds like it has a different cause and I need to start with > that assumption. Was that merged or is it still in -mm? The last thing I see in arch/x86_64/irq.c is: [PATCH] x86-64: survive having no irq mapping for a vector And we tried that one. - 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