linux-kernel - Re: [PATCH] cpusets: Make cpus_allowed and mems

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]

Date:	Mon, 6 Apr 2015 13:47:35 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Preeti U Murthy <preeti@...ux.vnet.ibm.com>
Cc:	Peter Zijlstra <peterz@...radead.org>, lizefan@...wei.com,
	anton@...ba.org, svaidy@...ux.vnet.ibm.com, rjw@...ysocki.net,
	paulmck@...ux.vnet.ibm.com, mingo@...nel.org,
	cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
	bharata@...ux.vnet.ibm.com
Subject: Re: [PATCH] cpusets: Make cpus_allowed and mems_allowed masks
 hotplug invariant

Hello, Preeti.

On Thu, Apr 02, 2015 at 12:26:32PM +0530, Preeti U Murthy wrote:
> By ensuring that the user configured cpusets are untouched, I don't see
> how we affect userspace adversely. The expectation usually is that the
> kernel keeps track of the user configurations. If anything we would be
> fixing an undesired behavior, wouldn't we?

The problem is not really about which behavior is "righter" but rather
it's fairly likely that there are users / tools out there expecting
the current behavior and they wouldn't be too happy to see the
behavior flipping underneath them.

One way forward would be implementing a knob in cpuset which makes it
switch sbetween the old and new behaviors in the legacy hierarchy.
It's yucky but doable if absoluately necessary, but what's the reason
for you not being able to transition to the unified hierarchy (except
for it being under the devel flag but I'm really taking that devel
mask out in the next merge window)?  The default hierarchy can happily
co-exist with legacy hierarchies so you can just move over the cpuset
part to it if you need it.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/