linux-kernel - Re: [PATCH] xen: fix booting ballooned down hvm guest

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: <5c91d54b-be9a-b454-bf76-d7d10159f1a2@suse.com>
Date:   Tue, 24 Oct 2017 16:58:11 +0200
From:   Juergen Gross <jgross@...e.com>
To:     Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org
Cc:     hw42@...umj.de, stable@...r.kernel.org
Subject: Re: [PATCH] xen: fix booting ballooned down hvm guest

On 24/10/17 16:56, Boris Ostrovsky wrote:
> On 10/24/2017 10:41 AM, Juergen Gross wrote:
>> On 24/10/17 16:33, Boris Ostrovsky wrote:
>>> On 10/24/2017 04:10 AM, Juergen Gross wrote:
>>>> Commit 96edd61dcf44362d3ef0bed1a5361e0ac7886a63 ("xen/balloon: don't
>>>> online new memory initially") introduced a regression when booting a
>>>> HVM domain with memory less than mem-max: instead of ballooning down
>>>> immediately the system would try to use the memory up to mem-max
>>>> resulting in Xen crashing the domain.
>>>>
>>>> For HVM domains the current size will be reflected in Xenstore node
>>>> memory/static-max instead of memory/target.
>>>>
>>>> Additionally we have to trigger the ballooning process at once.
>>>>
>>>> Cc: <stable@...r.kernel.org> # 4.13
>>>> Fixes: 96edd61dcf44362d3ef0bed1a5361e0ac7886a63 ("xen/balloon: don't
>>>>        online new memory initially")
>>>>
>>>> Suggested-by: Boris Ostrovsky <boris.ostrovsky@...cle.com>
>>>> Signed-off-by: Juergen Gross <jgross@...e.com>
>>> Reported-by: HW42 <hw42@...umj.de>
>> Hmm, is an anonymous Reported-by: tag okay?
> 
> Oh, I don't know what the rules are for this kind of address. I'd
> probably still add it but it's up to you.

The docs say each tag should be:

  tag: Full Name <email address>  optional-other-stuff

I don't think HW42 can be regarded to be a full name.


Juergen