mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
	Paul Menage <menage@google.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpuset: fix regression when failed to generate sched domains
Date: Tue, 18 Nov 2008 17:24:03 -0800	[thread overview]
Message-ID: <49236AB3.4040708@qualcomm.com> (raw)
In-Reply-To: <49225A5B.6080103@cn.fujitsu.com>

Li Zefan wrote:
> When cpuset failed to generate sched domains due to kmalloc()
> failure, the scheduler should fallback to the single partition
> 'fallback_doms' and rebuild sched domains, but now it only
> destroys but not rebuilds sched domains.
> 
> The regression is introduced by:
> 
> commit dfb512ec4834116124da61d6c1ee10fd0aa32bd6
> Author: Max Krasnyansky <maxk@qualcomm.com>
> Date:   Fri Aug 29 13:11:41 2008 -0700
> 
>     sched: arch_reinit_sched_domains() must destroy domains to force rebuild
> 
> After the above commit, partition_sched_domains(0, NULL, NULL) will
> only destroy sched domains and partition_sched_domains(1, NULL, NULL)
> will create the default sched domain.
> 
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>

Looks good to me. Thanx for the fix.

Max



> ---
> 
> Should I also CC stable for 2.6.27.xx ?
> 
> ---
>  kernel/cpuset.c |   12 ++++++++----
>  kernel/sched.c  |   13 +++++++------
>  2 files changed, 15 insertions(+), 10 deletions(-)
> 
> diff --git a/kernel/cpuset.c b/kernel/cpuset.c
> index 3e00526..81fc679 100644
> --- a/kernel/cpuset.c
> +++ b/kernel/cpuset.c
> @@ -587,7 +587,6 @@ static int generate_sched_domains(cpumask_t **domains,
>  	int ndoms;		/* number of sched domains in result */
>  	int nslot;		/* next empty doms[] cpumask_t slot */
>  
> -	ndoms = 0;
>  	doms = NULL;
>  	dattr = NULL;
>  	csa = NULL;
> @@ -674,10 +673,8 @@ restart:
>  	 * Convert <csn, csa> to <ndoms, doms> and populate cpu masks.
>  	 */
>  	doms = kmalloc(ndoms * sizeof(cpumask_t), GFP_KERNEL);
> -	if (!doms) {
> -		ndoms = 0;
> +	if (!doms)
>  		goto done;
> -	}
>  
>  	/*
>  	 * The rest of the code, including the scheduler, can deal with
> @@ -732,6 +729,13 @@ restart:
>  done:
>  	kfree(csa);
>  
> +	/*
> +	 * Fallback to the default domain if kmalloc() failed.
> +	 * See comments in partition_sched_domains().
> +	 */
> +	if (doms == NULL)
> +		ndoms = 1;
> +
>  	*domains    = doms;
>  	*attributes = dattr;
>  	return ndoms;
> diff --git a/kernel/sched.c b/kernel/sched.c
> index c94baf2..9b1e793 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -7789,13 +7789,14 @@ static int dattrs_equal(struct sched_domain_attr *cur, int idx_cur,
>   *
>   * The passed in 'doms_new' should be kmalloc'd. This routine takes
>   * ownership of it and will kfree it when done with it. If the caller
> - * failed the kmalloc call, then it can pass in doms_new == NULL,
> - * and partition_sched_domains() will fallback to the single partition
> - * 'fallback_doms', it also forces the domains to be rebuilt.
> + * failed the kmalloc call, then it can pass in doms_new == NULL &&
> + * ndoms_new == 1, and partition_sched_domains() will fallback to
> + * the single partition 'fallback_doms', it also forces the domains
> + * to be rebuilt.
>   *
> - * If doms_new==NULL it will be replaced with cpu_online_map.
> - * ndoms_new==0 is a special case for destroying existing domains.
> - * It will not create the default domain.
> + * If doms_new == NULL it will be replaced with cpu_online_map.
> + * ndoms_new == 0 is a special case for destroying existing domains,
> + * and it will not create the default domain.
>   *
>   * Call with hotplug lock held
>   */


      parent reply	other threads:[~2008-11-19  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-18  6:02 Li Zefan
2008-11-18  7:45 ` Ingo Molnar
2008-11-19  1:24 ` Max Krasnyansky [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=49236AB3.4040708@qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=menage@google.com \
    --cc=mingo@elte.hu \
    --cc=svaidy@linux.vnet.ibm.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

all inboxes | Powered by JetHome®