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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 18 Jan 2008 23:24:51 -0200 From: "Glauber de Oliveira Costa" <glommer@...il.com> To: "Ingo Molnar" <mingo@...e.hu> Cc: "Zachary Amsden" <zach@...are.com>, "Glauber de Oliveira Costa" <gcosta@...hat.com>, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, tglx@...utronix.de, ehabkost@...hat.com, jeremy@...p.org, avi@...ranet.com, anthony@...emonkey.ws, virtualization@...ts.linux-foundation.org, rusty@...tcorp.com.au, ak@...e.de, chrisw@...s-sol.org, rostedt@...dmis.org, hpa@...or.com, roland@...hat.com, mtosatti@...hat.com Subject: Re: [PATCH 0/10] Tree fixes for PARAVIRT On Jan 18, 2008 8:02 PM, Ingo Molnar <mingo@...e.hu> wrote: > > * Zachary Amsden <zach@...are.com> wrote: > > > > but in exchange you broke all of 32-bit with CONFIG_PARAVIRT=y. > > > Which means you did not even build-test it on 32-bit, let alone boot > > > test it... > > > > Why are we rushing so much to do 64-bit paravirt that we are breaking > > working configurations? If the developement is going to be this > > chaotic, it should be done and tested out of tree until it can > > stabilize. > > what you see is a open feedback cycle conducted on lkml. People send > patches for arch/x86, and we tell them if it breaks something. The bug > was found before i pushed out the x86.git devel tree (and the fix is > below - but this shouldnt matter to you because the bug never hit a > public x86.git tree). > > Ingo > Other than this, it seems to build and boot fine. Do you want me to resend ? -- Glauber de Oliveira Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act." -- 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