linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Cliff Wickman <cpw@sgi.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, travis@sgi.com,
	steiner@sgi.com
Subject: Re: [PULL] x86 cpumask work
Date: Wed, 18 Mar 2009 08:22:30 +1030	[thread overview]
Message-ID: <200903180822.31196.rusty@rustcorp.com.au> (raw)
In-Reply-To: <E1LjeSk-0004BW-3x@eag09.americas.sgi.com>

On Wednesday 18 March 2009 05:26:30 Cliff Wickman wrote:
> 
> From: Cliff Wickman <cpw@sgi.com>
> 
> A patch on Mar13 2009 introduced a bug. I hope the below 1-line fix can
> make the 'urgent' list, and get fixed before that patch moves on.
> 
> The Mar13 patch is saved at
> http://marc.info/?l=linux-kernel&m=123683186504948&w=2
> 
> The allocation of per-cpu uv_flush_tlb_mask's in arch/x86/kernel/tlb_uv.c
> changed a variable that should been reset to 0.

Hi Cliff,

   Thanks for tracking this.  May I suggest this slightly enhanced version?

Subject: cpumask: fix tlb_uv initialization

Impact: fix boot on UV systems

Commit 76ba0ecda0de9accea9a91cb6dbde46782110e1c "cpumask: use cpumask_var_t
in uv_flush_tlb_others" used cur_cpu as an iterator; it was supposed to be
zero for the code below it.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

diff --git a/arch/x86/kernel/tlb_uv.c b/arch/x86/kernel/tlb_uv.c
index 8afb691..deb5ebb 100644
--- a/arch/x86/kernel/tlb_uv.c
+++ b/arch/x86/kernel/tlb_uv.c
@@ -751,7 +751,7 @@ static int __init uv_bau_init(void)
 	int node;
 	int nblades;
 	int last_blade;
-	int cur_cpu = 0;
+	int cur_cpu;
 
 	if (!is_uv_system())
 		return 0;
@@ -765,6 +765,7 @@ static int __init uv_bau_init(void)
 	uv_mmask = (1UL << uv_hub_info->n_val) - 1;
 	nblades = 0;
 	last_blade = -1;
+	cur_cpu = 0;
 	for_each_online_node(node) {
 		blade = uv_node_to_blade_id(node);
 		if (blade == last_blade)


  reply	other threads:[~2009-03-17 21:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 18:56 [PULL] x86 cpumask work Cliff Wickman
2009-03-17 21:52 ` Rusty Russell [this message]
2009-03-18  8:51   ` [tip:x86/uv] x86, uv: fix cpumask iterator in uv_bau_init() Rusty Russell
2009-03-18 12:57   ` [PULL] x86 cpumask work Cliff Wickman
  -- strict thread matches above, loose matches on Subject: below --
2009-03-12  4:23 Rusty Russell
2009-03-12 10:26 ` Ingo Molnar
2009-03-12 10:37   ` Ingo Molnar
2009-03-12 22:54     ` Rusty Russell
2009-03-13  0:57       ` Ingo Molnar
2009-03-13  2:46         ` Rusty Russell
2009-03-13  3:20           ` Ingo Molnar
2009-03-13  4:34             ` Rusty Russell
2009-03-13  4:55               ` Ingo Molnar
2009-03-13  5:27                 ` Ingo Molnar
2009-03-13  5:32                   ` Ingo Molnar
2009-03-13  6:44                     ` Rusty Russell
2009-03-13 13:12                     ` Rusty Russell
2009-03-13 15:27                       ` Ingo Molnar
2009-03-15  2:56                         ` Rusty Russell
2009-03-15  6:00                           ` Ingo Molnar
2009-03-16  3:03                             ` Rusty Russell
2009-03-16  8:48                               ` Ingo Molnar
2009-03-17  4:20                                 ` Rusty Russell
2009-03-17 10:51                                   ` Ingo Molnar
2009-03-17 21:27                                     ` Rusty Russell

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=200903180822.31196.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=cpw@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=steiner@sgi.com \
    --cc=travis@sgi.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;
as well as URLs for NNTP newsgroup(s).