| 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
| ||
|
Message-Id: <1160133260.1607.60.camel@localhost.localdomain> Date: Fri, 06 Oct 2006 12:14:20 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Andi Kleen <ak@...e.de> Cc: Jeff Garzik <jeff@...zik.org>, discuss@...-64.org, torvalds@...l.org, linux-kernel@...r.kernel.org Subject: Re: [discuss] Re: Please pull x86-64 bug fixes Ar Iau, 2006-10-05 am 23:44 +0200, ysgrifennodd Andi Kleen: > I think we had that argument before. IMHO such messages are completely > useless. Hangs are not acceptable no matter what messages are printed > before. Oh so you plan to fix the iommu/aacraid problem you always said you wouldn't fix ? > > That gets us the best of both worlds. > > Hanging systems? Working systems because the only hang case will be if you use hardware that requires the new goodies on a box that is *actually* broken rather than one which is misdetected by the paranoid check code. Alan - 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