linux-kernel - Re: [RFC] Restrict kernel spawning of threads to a specified set of cpus.

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: <00000141179222e5-8a10141c-7b95-4204-853c-ab266fd08532-000000@email.amazonses.com>
Date:	Fri, 13 Sep 2013 13:45:55 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Gilad Ben-Yossef <gilad@...yossef.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Mike Frysinger <vapier@...too.org>,
	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [RFC] Restrict kernel spawning of threads to a specified set of
 cpus.

On Thu, 12 Sep 2013, Frederic Weisbecker wrote:

> So yeah it's a problem in theory. Now in practice, I have yet to be convinced because
> this should be solved after a few iterations in /proc in most cases.

I have seen some drivers regularly spawning threads all over the machnine.
This is a practical issue that I am addresing.
>
> Now the issue doesn't only concern kthreads but all tasks in the system.
> If we really want to solve that race, then may be we can think of a kernel_parameter
> that sets the initial affinity of init and then lets get it naturally inherited
> through the whole tree.

This patch that we are discussing does exactly that.

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