linux-kernel - Re: [Xen-devel] [PATCH] fixes to stable/for-linus-3.5

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: <4FBD0A19.30701@citrix.com>
Date:	Wed, 23 May 2012 17:02:33 +0100
From:	David Vrabel <david.vrabel@...rix.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC:	<linux-kernel@...r.kernel.org>, <david.vrabel@...rix.com>,
	<xen-devel@...ts.xensource.com>
Subject: Re: [Xen-devel] [PATCH] fixes to stable/for-linus-3.5

On 21/05/12 22:42, Konrad Rzeszutek Wilk wrote:
> 
> The autoballoon one would try to balloon up to E820_MAX when
> there were no dom0_mem=.. argument.

I don't see this behaviour and looking at the code I don't see how it
could.  The autoballoon code only populates pages that were released so
it won't go above xen_start_info->nr_pages.

Do you have any logs showing the problem behaviour?

> The patch fixes it, and
> is also makes the dom0_mem=1G case work better (I think?). The
> other solution would be to use the current_reservation patch
> I posted a while back to work-around when no dom0_mem= argument
> is used.

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/