linux-kernel - Re: [External] Re: [PATCH] cpuset: introduce non-blocking cpuset.mems setting option

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: <aC90-jGtD_tJiP5K@slm.duckdns.org>
Date: Thu, 22 May 2025 09:03:22 -1000
From: Tejun Heo <tj@...nel.org>
To: Zhongkun He <hezhongkun.hzk@...edance.com>
Cc: Waiman Long <llong@...hat.com>, hannes@...xchg.org,
	cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
	muchun.song@...ux.dev
Subject: Re: [External] Re: [PATCH] cpuset: introduce non-blocking
 cpuset.mems setting option

Hello,

On Thu, May 22, 2025 at 11:37:44AM +0800, Zhongkun He wrote:
> > I don't think this is a good idea. O_NONBLOCK means "don't wait", not "skip
> > this".
> 
> Yes, I agree.  However, we have been experiencing this issue for a long time,
> so we hope to have an option to disable memory migration in v2.
> 
> Would it be possible to re-enable the memory.migrate interface and
> disable memory migration by default in v2?
> 
> Alternatively, could we introduce an option in cpuset.mems to explicitly
> indicate that memory migration should not occur?
> 
> Please feel free to share any suggestions you might have.

Is this something you want on the whole machine? If so, would global cgroup
mount option work?

Thanks.

-- 
tejun