linux-kernel - Re: [patch] cpuset: fix crash when adding CPUs to an empty set

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: <20150128115332.GD23038@twins.programming.kicks-ass.net>
Date:	Wed, 28 Jan 2015 12:53:32 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Zefan Li <lizefan@...wei.com>
Cc:	Mike Galbraith <umgwanakikbuti@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [patch] cpuset: fix crash when adding CPUs to an empty set

On Wed, Jan 28, 2015 at 12:24:52PM +0800, Zefan Li wrote:
> > sched: Fix crash if cpuset_cpumask_can_shrink() is passed an empty cpumask
> > 
> > While creating an exclusive cpuset, we passed cpuset_cpumask_can_shrink()
> > an empty cpumask (cur), and dl_bw_of(cpumask_any(cur)) made boom with it.
> > 

Is this the case where a new cpuset doesn't yet have CPUs assigned?

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