linux-kernel - Re: [PATCH v2] mm, page_alloc: fix build_zonerefs

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]

Message-ID: <fa36ede3-3f5c-e10c-107d-0e4fae4af098@suse.com>
Date:   Fri, 8 Apr 2022 07:50:04 +0200
From:   Juergen Gross <jgross@...e.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     xen-devel@...ts.xenproject.org, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Marek Marczykowski-Górecki 
        <marmarek@...isiblethingslab.com>, Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH v2] mm, page_alloc: fix build_zonerefs_node()

On 08.04.22 00:44, Andrew Morton wrote:
> On Thu,  7 Apr 2022 14:06:37 +0200 Juergen Gross <jgross@...e.com> wrote:
> 
>> Since commit 6aa303defb74 ("mm, vmscan: only allocate and reclaim from
>> zones with pages managed by the buddy allocator")
> 
> Six years ago!
> 
>> only zones with free
>> memory are included in a built zonelist. This is problematic when e.g.
>> all memory of a zone has been ballooned out when zonelists are being
>> rebuilt.
>>
>> The decision whether to rebuild the zonelists when onlining new memory
>> is done based on populated_zone() returning 0 for the zone the memory
>> will be added to. The new zone is added to the zonelists only, if it
>> has free memory pages (managed_zone() returns a non-zero value) after
>> the memory has been onlined. This implies, that onlining memory will
>> always free the added pages to the allocator immediately, but this is
>> not true in all cases: when e.g. running as a Xen guest the onlined
>> new memory will be added only to the ballooned memory list, it will be
>> freed only when the guest is being ballooned up afterwards.
>>
>> Another problem with using managed_zone() for the decision whether a
>> zone is being added to the zonelists is, that a zone with all memory
>> used will in fact be removed from all zonelists in case the zonelists
>> happen to be rebuilt.
>>
>> Use populated_zone() when building a zonelist as it has been done
>> before that commit.
>>
>> Cc: stable@...r.kernel.org
> 
> Some details, please.  Is this really serious enough to warrant
> backporting?  Is some new workload/usage pattern causing people to hit
> this?

Yes. There was a report that QubesOS (based on Xen) is hitting this
problem. Xen has switched to use the zone device functionality in
kernel 5.9 and QubesOS wants to use memory hotplugging for guests in
order to be able to start a guest with minimal memory and expand it
as needed. This was the report leading to the patch.


Juergen


Download attachment "OpenPGP_0xB0DE9DD628BF132F.asc" of type "application/pgp-keys" (3099 bytes)

Download attachment "OpenPGP_signature" of type "application/pgp-signature" (496 bytes)