linux-kernel - Re: patch] cpusets, 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: <1318928763.21167.5.camel@twins>
Date:	Tue, 18 Oct 2011 11:06:03 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Mike Galbraith <efault@....de>
Cc:	LKML <linux-kernel@...r.kernel.org>, Tejun Heo <htejun@...il.com>,
	Li Zefan <lizf@...fujitsu.com>,
	Paul Menage <paul@...lmenage.org>,
	David Rientjes <rientjes@...gle.com>
Subject: Re: patch] cpusets, cgroups: disallow attaching kthreadd

On Tue, 2011-10-18 at 10:47 +0200, Mike Galbraith wrote:
> On Tue, 2011-10-18 at 10:42 +0200, Peter Zijlstra wrote:
> 
> > Why special case these two, why not simply disallow moving kthreadd into
> > _any_ cgroup what so ever and be done with it?
> 
> These were the cases where it hurt, and cpusets don't have to be a
> component of a cgroup.  So we'd still need the cpuset bit.

but but but,, cpusetes are a cgroup thingy?!

> > 
> > ---
> > diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> > index 453100a..18eed58 100644
> > --- a/kernel/cgroup.c
> > +++ b/kernel/cgroup.c
> > @@ -1824,6 +1824,9 @@ int cgroup_attach_task(struct cgroup *cgrp, struct task_struct *tsk)
> >  	struct cgroup *oldcgrp;
> >  	struct cgroupfs_root *root = cgrp->root;
> >  
> > +	if (tsk == kthreadd_task)
> > +		return -EINVAL;
> > +
> >  	/* Nothing to do if the task is already in that cgroup */
> >  	oldcgrp = task_cgroup_from_root(tsk, root);
> >  	if (cgrp == oldcgrp)
> > 
> 
> 

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