| 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: <20090203173612.GA3528@elte.hu> Date: Tue, 3 Feb 2009 18:36:12 +0100 From: Ingo Molnar <mingo@...e.hu> To: Jeremy Fitzhardinge <jeremy@...p.org> Cc: "H. Peter Anvin" <hpa@...or.com>, the arch/x86 maintainers <x86@...nel.org>, Xen-devel <xen-devel@...ts.xensource.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] xen: fix 32-bit build resulting from mmu move * Jeremy Fitzhardinge <jeremy@...p.org> wrote: > Ingo Molnar wrote: >> * Jeremy Fitzhardinge <jeremy@...p.org> wrote: >> >> >>> Moving the mmu code from enlighten.c to mmu.c inadvertently broke the >>> 32-bit build. Fix it. >>> >>> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com> >>> --- >>> arch/x86/xen/mmu.c | 37 +++++++++++++++++++++++++++++++++++++ >>> 1 file changed, 37 insertions(+) >>> >> >> that goes on top of the recent tip/x86/paravirt changes, right? No >> objections, i'm wondering why my testing didnt find any build breakage. >> Could you send me a .config that triggers the breakage? > > Any x86-32 + Xen build would hit it. +highmem+highpte would break a bit > more. i have a lot of successful builds with that pattern, that's why i asked for a specific config from you that definitely triggers it - i'd like to investigate how it escaped my testing procedures. Ingo -- 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