linux-kernel - Re: Fix for xen guest with mem

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: <20080914132104.GB32106@elte.hu>
Date:	Sun, 14 Sep 2008 15:21:04 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	roberto@...it.it, jeremy@...source.com,
	linux-kernel@...r.kernel.org, Mirko Iannella <mirko@...it.it>,
	Alex Nixon <alex.nixon@...rix.com>
Subject: Re: Fix for xen guest with mem > 3.7G


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> Roberto De Ioris wrote:
> > Xen domU kernel 2.6.26 and 2.6.27-rc cannot allocate
> > more than 3.7GB of ram on my PAE systems (compiled
> > with gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)).
> >
> > I have found the problem is in function xen_memory_setup (in
> > arch/x86/xen/setup.c).
> >
> > It set max_pfn as 'unsigned long' but add_memory_region()
> > takes 'unsigned long long'.
> >
> > I do not know if it is a compiler problem but this is the simple fix
> > (works on my systems):
> >   
> 
> Thanks very much for the patch.  We have a more general fix for this in
> Ingo's tip.git tree, but I overlooked that this particular problem
> affected current -rc.
> 
> Ingo, this is fixed by the phys_addr_t + PFN_PHYS() patches.  Should 
> we send them up to Linus, or do an ad-hoc fix in this one place?

send an ad-hoc fix please .. the phys_addr_t patches have a too wide 
impact i think.

	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/