linux-kernel - Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen support

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4865147B.50202@goop.org>
Date:	Fri, 27 Jun 2008 09:25:31 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Nick Piggin <npiggin@...e.de>, Mark McLoughlin <markmc@...hat.com>,
	xen-devel <xen-devel@...ts.xensource.com>,
	Eduardo Habkost <ehabkost@...hat.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	Stephen Tweedie <sct@...hat.com>, x86@...nel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for
 64-bit Xen support

Ingo Molnar wrote:
> yeah, i guess so. Right now i only ran into the build failure so there's 
> hope :) Here's a config that fails to build for sure:
>
>   http://redhat.com/~mingo/misc/config-Fri_Jun_27_17_54_32_CEST_2008.bad
>   

Will look at it shortly.

> note, on 32-bit there's a yet unfixed initrd corruption bug i've 
> bisected back to:
>
> | 510be56adc4bb9fb229637a8e89268d987263614 is first bad commit
> | commit 510be56adc4bb9fb229637a8e89268d987263614
> | Author: Yinghai Lu <yhlu.kernel@...il.com>
> | Date:   Tue Jun 24 04:10:47 2008 -0700
> |
> |    x86: introduce init_memory_mapping for 32bit
>
> so if you see something like that it's probably not a bug introduced by 
> your changes. (and maybe you'll see why the above commit is buggy, i 
> havent figured it out yet)

Well, on a non-PSE system find_early_table_space() will not allocate 
enough memory for ptes.  But I posted the fix for that, and it's likely 
you're using PSE anyway.  Nothing pops out from a quick re-read, but it 
could easily be mis-reserving the ramdisk memory or something.

    J
--
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/