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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 19 Oct 2011 07:28:16 +0200
From:	Mike Galbraith <efault@....de>
To:	Paul Menage <paul@...lmenage.org>
Cc:	David Rientjes <rientjes@...gle.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	LKML <linux-kernel@...r.kernel.org>,
	Tejun Heo <htejun@...il.com>, Li Zefan <lizf@...fujitsu.com>
Subject: Re: patch] cpusets, cgroups: disallow attaching kthreadd

On Tue, 2011-10-18 at 21:56 -0700, Paul Menage wrote:
> On Tue, Oct 18, 2011 at 9:53 PM, Paul Menage <paul@...lmenage.org> wrote:
> >
> > I can see the argument that the number of use-cases for this is fairly
> > small, but in line with the principle of keeping the ABI as stable as
> > possible in the absence of bugs that force a change, having the
> > restriction in the necessary subsystems seems cleaner.
> >
> 
> Separately, an alternative fix for the cpusets case be to make it
> always possible to move a thread to the root cpuset, even if it's
> PF_THREAD_BOUND?

Yeah, an escape hatch is what I did first.

https://lkml.org/lkml/2011/9/23/14

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