linux-kernel - Re: [Xen-devel] [PATCH] xen: limit memory to architectural maximum

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] [day] [month] [year] [list]

Date:	Fri, 4 Sep 2015 16:43:45 +0100
From:	David Vrabel <david.vrabel@...rix.com>
To:	Juergen Gross <jgross@...e.com>, <linux-kernel@...r.kernel.org>,
	<xen-devel@...ts.xensource.com>, <konrad.wilk@...cle.com>,
	<david.vrabel@...rix.com>, <boris.ostrovsky@...cle.com>
Subject: Re: [Xen-devel] [PATCH] xen: limit memory to architectural maximum

On 04/09/15 13:18, Juergen Gross wrote:
> When a pv-domain (including dom0) is started it tries to size it's
> p2m list according to the maximum possible memory amount it ever can
> achieve. Limit the initial maximum memory size to the architectural
> limit of the hardware in order to avoid overflows during remapping
> of memory.
> 
> This problem will occur when dom0 is started with an initial memory
> size being a multiple of 1GB, but without specifying it's maximum
> memory size. The kernel must be configured without
> CONFIG_XEN_BALLOON_MEMORY_HOTPLUG for the problem to happen.

Applied to for-linus-4.3, thanks.

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