Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751914AbbFBTHc (ORCPT ); Tue, 2 Jun 2015 15:07:32 -0400 Received: from mail-ig0-f182.google.com ([209.85.213.182]:36781 "EHLO mail-ig0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751725AbbFBTHX (ORCPT ); Tue, 2 Jun 2015 15:07:23 -0400 MIME-Version: 1.0 In-Reply-To: <1432179674-19154-1-git-send-email-john.stultz@linaro.org> References: <1432179674-19154-1-git-send-email-john.stultz@linaro.org> Date: Tue, 2 Jun 2015 12:07:23 -0700 Message-ID: Subject: Re: [RFC][PATCH 0/2] Android style loosening of cgroup attach permissions From: John Stultz To: lkml Cc: John Stultz , Tejun Heo , Li Zefan , Jonathan Corbet , cgroups@vger.kernel.org, Android Kernel Team , Rom Lemarchand , Colin Cross Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1172 Lines: 27 On Wed, May 20, 2015 at 8:41 PM, John Stultz wrote: > As a heads up, this is just a first RFC and not a submission. > > Android currently loosens the cgroup attchment permissions, allowing > tasks with CAP_SYS_NICE to be able to allow tasks to move arbitrary > tasks across cgroups. > > At first glance, overloading CAP_SYS_NICE seems a bit hackish, but this > shows that there is a active and widely deployed use for different cgroup > attachment rules then what is currently available. > > I've tried to rework the patches so this attachment policy is build > time configurable, and wanted to send them out for review so folks > might give their thoughts on this implementation and what they might > see as a better way to go about achieving the same goal. > > Thoughts and feedback would be appriciated! Ping? Not sure if I hit folks at a busy time or if I didn't cc the right folks? thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/