public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dino@in.ibm.com, cpw@sgi.com, menage@google.com,
	linux-kernel@vger.kernel.org, randy.dunlap@oracle.com,
	nickpiggin@yahoo.com.au, mingo@elte.hu
Subject: Re: [PATCH v2] cpuset sched_load_balance flag
Date: Wed, 10 Oct 2007 20:10:08 -0700	[thread overview]
Message-ID: <20071010201008.50854faf.pj@sgi.com> (raw)
In-Reply-To: <20071010192957.78d3668f.akpm@linux-foundation.org>

> > +		doms = kmalloc(sizeof(cpumask_t), GFP_KERNEL);
> > +		*doms = top_cpuset.cpus_allowed;
> 
> We generally only excuse failure to check kmalloc return value when the
> code is called on the bootup path.  But this code is called at other times.
> 
> >
> > ...
> > +	doms_cur =  kmalloc(sizeof(cpumask_t), GFP_KERNEL);

Ah - good catch - thanks, Andrew.  I should put together a fix,
to check these kmalloc calls.

For rebuild_sched_domains(), this can mean we just up and return having
done nothing.

For arch_init_sched_domains(), the code calling arch_init_sched_domains()
is not checking for failure, and doesn't have a trivial fallback code
path in the case of failure.  I'll have to think about that one just a
little.

Thanks, Andrew!

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

      reply	other threads:[~2007-10-11  3:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-06  9:47 [PATCH v2] cpuset sched_load_balance flag Paul Jackson
2007-10-06 11:17 ` Ingo Molnar
2007-10-11  2:29 ` Andrew Morton
2007-10-11  3:10   ` Paul Jackson [this message]

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=20071010201008.50854faf.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=cpw@sgi.com \
    --cc=dino@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox