linux-kernel - Re: [patch] cgroups: disallow attaching kthreadd

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1333604949.7783.76.camel@marge.simpson.net>
Date:	Thu, 05 Apr 2012 07:49:09 +0200
From:	Mike Galbraith <mgalbraith@...e.de>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Tejun Heo <tj@...nel.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Menage <paul@...lmenage.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Li Zefan <lizefan@...wei.com>
Subject: Re: [patch] cgroups: disallow attaching kthreadd

On Wed, 2012-04-04 at 21:58 -0700, David Rientjes wrote: 
> On Thu, 5 Apr 2012, Mike Galbraith wrote:
> 
> > Below is user interface only patchlet.  I find it cleaner than the
> > cpuset,cpu variant, but don't have strong feelings either way.
> > 
> > If this one don't fly, I'll just declare buglet immortal, he ain't worth
> > near the electrons he's already wasted ;-) 
> > 
> 
> Why can't you simply propose the cpusets version that both Paul and I 
> liked?  There's _no_ reason to do this for every cgroup, current or 
> future.

I submitted that, and it didn't fly.  I like the generic exclusion
better, so I submit that for consideration.

>From my POV, the problem is known, decision makers can decide any way
they want, but _I_ have posted my last variant.  If this one doesn't
fly, too bad for patchlet, it's not the first one to ever go splat :)

-Mike


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