linux-kernel - Re: [PATCH V2] cpuset: Add knob to make allowed masks hotplug invariant on legacy hierarchy

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: <552FA3B4.6080905@linux.vnet.ibm.com>
Date:	Thu, 16 Apr 2015 17:27:40 +0530
From:	Preeti U Murthy <preeti@...ux.vnet.ibm.com>
To:	"Serge E. Hallyn" <serge@...lyn.com>, Tejun Heo <tj@...nel.org>
CC:	Peter Zijlstra <peterz@...radead.org>, svaidy@...ux.vnet.ibm.com,
	nacc@...ux.vnet.ibm.com, rjw@...ysocki.net,
	linux-kernel@...r.kernel.org, lizefan@...wei.com, anton@...ba.org,
	bharata@...ux.vnet.ibm.com, cgroups@...r.kernel.org,
	paulmck@...ux.vnet.ibm.com, mingo@...nel.org
Subject: Re: [PATCH V2] cpuset: Add knob to make allowed masks hotplug invariant
 on legacy hierarchy

On 04/15/2015 10:06 PM, Serge E. Hallyn wrote:
> On Wed, Apr 15, 2015 at 12:18:11PM -0400, Tejun Heo wrote:
>> On Wed, Apr 15, 2015 at 11:15:35AM -0500, Serge E. Hallyn wrote:
>>> The reason would be because it breaks "legacy" software.  So that
>>> would only matter if Preeti needs to run such software.
>>
>> Sure, I get that argument but this is changing how the contorller
>> behaves in a major way.
> 
> It is.  My main counter to that would be that it is how cpusets
> should always have worked :)
> 
>>   There are specifics which may make this
>> particular case more justifiable but overall the combination of
>> arguments is pretty weird.
> 
> And becomes harder to reason about and review/maintain.  I agree
> there.
> 
> From userspace, I suppose one approach (though note it is racy) to
> solving this would be to have udev rules which
> 
> . On cpu unplug, record all cgroups which were using that cpu
> . on cpu plug, re-add the cpu to all recorded cgroups for that
> cpu (if any), as well as to any cgroups marked (in some /etc
> file) as using "all" or a percentage of all cpus.

Yes this is the best way to move forward. But the stacks in userspace
that manage cgroups need to each have such a daemon managing the cpusets
like is pointed above. It would have been fair to expect them to do this
except that this is one issue that userspace is expecting the kernel to
handle. The side effects of this behavior of the legacy hierarchy is
showing up in weird ways.

Another approach as Tejun pointed is to switch over to the unified
hierarchy. I can test this out (How do we mount specific controllers in
the unified hierarchy Tejun? It does not allow any mount options today),
but I don't think I can exhaustively test this out by myself across
distros. So I am not confident of this approach.

The last approach would be as Peter pointed, mimick the entire unified
hierarchy through a mount option, similar to the SANE_BEHAVIOR option
that was present earlier and was removed. Tejun ? Can we bring back that
mount option ?

Regards
Preeti U Murthy
> 
> -serge
> 

--
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/