linux-kernel - Re: MPOL_BIND on memory only nodes

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: <20161013100708.GI21678@dhcp22.suse.cz>
Date:   Thu, 13 Oct 2016 12:07:09 +0200
From:   Michal Hocko <mhocko@...nel.org>
To:     Anshuman Khandual <khandual@...ux.vnet.ibm.com>
Cc:     Mel Gorman <mgorman@...e.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Memory Management List <linux-mm@...ck.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
        Balbir Singh <bsingharora@...il.com>,
        Vlastimil Babka <vbabka@...e.cz>,
        Minchan Kim <minchan@...nel.org>
Subject: Re: MPOL_BIND on memory only nodes

On Thu 13-10-16 15:24:54, Anshuman Khandual wrote:
[...]
> Which makes the function look like this. Even with these changes, MPOL_BIND is
> still going to pick up the local node's zonelist instead of the first node in
> policy->v.nodes nodemask. It completely ignores policy->v.nodes which it should
> not.

Not really. I have tried to explain earlier. We do not ignore policy
nodemask. This one comes from policy_nodemask. We start with the local
node but fallback to some of the nodes from the nodemask defined by the
policy.
-- 
Michal Hocko
SUSE Labs