linux-kernel - Re: [PATCH] xen/balloon: fix balloon initialization for PVH Dom0

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

Date:   Wed, 8 Aug 2018 13:01:23 -0400
From:   Boris Ostrovsky <boris.ostrovsky@...cle.com>
To:     Roger Pau Monne <roger.pau@...rix.com>,
        linux-kernel@...r.kernel.org
Cc:     Gabriel Ercarug <bercarug@...zon.com>,
        Juergen Gross <jgross@...e.com>, xen-devel@...ts.xenproject.org
Subject: Re: [PATCH] xen/balloon: fix balloon initialization for PVH Dom0

On 08/08/2018 07:46 AM, Roger Pau Monne wrote:
> The current balloon code tries to calculate a delta factor for the
> balloon target when running in HVM mode in order to account for memory
> used by the firmware.
>
> This workaround for memory accounting doesn't work properly on a PVH
> Dom0, that has a static-max value different from the target value even
> at startup. Note that this is not a problem for DomUs because guests are
> started with a static-max value that matches the amount of RAM in the
> memory map.
>
> Fix this by forcefully setting target_diff for Dom0, regardless of
> it's mode.
>
> Reported-by: Gabriel Bercarug <bercarug@...zon.com>
> Signed-off-by: Roger Pau Monné <roger.pau@...rix.com>
>


Applied to for-linus-4.19

-boris