From: David S. Miller <davem@davemloft.net>
Date: Wed, 9 Mar 2011 21:00:47 +0000 (-0800)
Subject: sparc32: Fix might-be-used-uninitialized warning in do_sparc_fault().
X-Git-Tag: v2.6.39-rc1~459^2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=c816be7b5f24585baa9eba1f2413935f771d6ad6;p=platform%2Fkernel%2Flinux-stable.git

sparc32: Fix might-be-used-uninitialized warning in do_sparc_fault().

When we try to handle vmalloc faults, we can take a code
path which uses "code" before we actually set it.

Amusingly gcc-3.3 notices this yet gcc-4.x does not.

Reported-by: Bob Breuer <breuerr@mc.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
---

diff --git a/arch/sparc/mm/fault_32.c b/arch/sparc/mm/fault_32.c
index 5b836f5..b10ac4d 100644
--- a/arch/sparc/mm/fault_32.c
+++ b/arch/sparc/mm/fault_32.c
@@ -240,11 +240,10 @@ asmlinkage void do_sparc_fault(struct pt_regs *regs, int text_fault, int write,
 	 * only copy the information from the master page table,
 	 * nothing more.
 	 */
+	code = SEGV_MAPERR;
 	if (!ARCH_SUN4C && address >= TASK_SIZE)
 		goto vmalloc_fault;
 
-	code = SEGV_MAPERR;
-
 	/*
 	 * If we're in an interrupt or have no user
 	 * context, we must not take the fault..