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: <0e99b72c-c3d9-424e-8efe-af750da69ebf@ustc.edu>
Date: Mon, 29 Jan 2024 14:15:00 +0800
From: ustc <luochunsheng@...c.edu>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mempolicy: check home_node is in the nodes of policy

For example,  In a system with NUMA nodes 0,1,2,3, i mbind process to 
node 0-2 and set home_node to node 3, it will not be allocated from node 
3, then from node closer to node 3. But i think home_node should be set 
directly from node 0-2, which makes more sense. So i think it needs to 
return failure to prompt user.


On 2024/1/28 16:29, Andrew Morton wrote:
> On Fri, 26 Jan 2024 08:22:40 -0500 Chunsheng Luo <luochunsheng@...c.edu> wrote:
>
>> set_mempolicy_home_node should be used after setting the memory
>> policy. If the home_node isn't in the nodes of policy, we should
>> return failure to avoid misunderstanding.
> Thanks.  Under what circumstances does userspace trigger this issue?
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ