From: Peter Zijlstra <peterz@infradead.org>
To: Zefan Li <lizefan@huawei.com>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [patch] cpuset: fix crash when adding CPUs to an empty set
Date: Wed, 28 Jan 2015 12:53:32 +0100 [thread overview]
Message-ID: <20150128115332.GD23038@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <54C86494.6020509@huawei.com>
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?
next prev parent reply other threads:[~2015-01-29 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 6:16 [patch] cpuset: fix crash when adding CPUs to an empty set Mike Galbraith
2015-01-28 2:41 ` Zefan Li
2015-01-28 3:53 ` Mike Galbraith
2015-01-28 4:24 ` Zefan Li
2015-01-28 11:53 ` Peter Zijlstra [this message]
2015-01-28 12:03 ` Mike Galbraith
2015-01-28 14:33 ` [tip:sched/urgent] sched: Fix crash if cpuset_cpumask_can_shrink( ) is passed an empty cpumask tip-bot for Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150128115332.GD23038@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=umgwanakikbuti@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.