linux-kernel - Re: [git pull] xen, x86 fixes

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4860EB57.30402@goop.org>
Date:	Tue, 24 Jun 2008 08:40:55 -0400
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Adrian Bunk <bunk@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	the arch/x86 maintainers <x86@...nel.org>,
	Rusty Russell <rusty@...tcorp.com.au>, chrisw@...s-sol.org,
	xen-devel@...ts.xensource.com
Subject: Re: [git pull] xen, x86 fixes

Adrian Bunk wrote:
> Another compile error from the x86 tree:
>
> <--  snip  -->
>
> ...
>   CC      arch/x86/xen/mmu.o
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/x86/xen/mmu.c: In function ‘xen_pmd_val’:
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/x86/xen/mmu.c:229: error: ‘pmd_t’ has no member named ‘pmd’
> make[2]: *** [arch/x86/xen/mmu.o] Error 1
>
> <--  snip  -->
>
> The problem seems to be related to CONFIG_X86_PAE=n which results in
> PAGETABLE_LEVELS == 2.
>
> Not visible in -next due to "xen: remove support for non-PAE 32-bit",
> but that is not in 2.6.26.
>   

Thanks Adrian,

Bringing that patch over into .26 would be the easiest fix.  It's 
effectively a bugfix because non-PAE Xen is broken and unusable anyway.

Alternatively, I can easily put a little patch together to use the right 
accessors that will compile in non-PAE.

    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/