linux-kernel - Re: [PATCH v2 2/2] drivers/base/memory: determine and store zone for single-zone memory blocks

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: <Yg0cGbrTA4bDEQHx@localhost.localdomain>
Date:   Wed, 16 Feb 2022 16:45:29 +0100
From:   Oscar Salvador <osalvador@...e.de>
To:     David Hildenbrand <david@...hat.com>
Cc:     linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Michal Hocko <mhocko@...e.com>,
        Rafael Parra <rparrazo@...hat.com>
Subject: Re: [PATCH v2 2/2] drivers/base/memory: determine and store zone for
 single-zone memory blocks

On Wed, Feb 16, 2022 at 02:46:56PM +0100, David Hildenbrand wrote:
> And yes, add_memory_block() chould __init, that would also make it
> clearer out of which context init_memory_block() is called with
> MEM_ONLINE. I can send an addon patch for that!

Yeah, I think that would have helped me, and it definitely makes it more
clear, so go ahead ;-)


-- 
Oscar Salvador
SUSE Labs