linux-kernel - Re: [PATCH v3 3/5] cpusets: Update tasks' cpus_allowed mask upon updates to root cpuset

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: <alpine.DEB.2.00.1205141731180.25235@chino.kir.corp.google.com>
Date:	Mon, 14 May 2012 17:31:29 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
cc:	a.p.zijlstra@...llo.nl, mingo@...nel.org, pjt@...gle.com,
	paul@...lmenage.org, akpm@...ux-foundation.org, rjw@...k.pl,
	nacc@...ibm.com, paulmck@...ux.vnet.ibm.com, tglx@...utronix.de,
	seto.hidetoshi@...fujitsu.com, tj@...nel.org, mschmidt@...hat.com,
	berrange@...hat.com, nikunj@...ux.vnet.ibm.com,
	vatsa@...ux.vnet.ibm.com, liuj97@...il.com,
	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v3 3/5] cpusets: Update tasks' cpus_allowed mask upon
 updates to root cpuset

On Mon, 14 May 2012, Srivatsa S. Bhat wrote:

> The root cpuset's cpus_allowed mask can get updated during CPU hotplug.
> However, during those updates, the tasks belonging to the root cpuset
> aren't touched at all - their cpus_allowed masks aren't updated to reflect
> the change in the configuration of the cpuset they belong to.
> 
> Fix this by moving the update of top_cpuset.cpus_allowed to
> scan_cpusets_upon_hotplug() and ensure that the call to update_tasks_cpumask()
> is not missed out for the root cpuset, including for cpu online events.
> 
> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@...ux.vnet.ibm.com>

Acked-by: David Rientjes <rientjes@...gle.com>
--
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/