David Miller wrote: > From: Bob Breuer <breuerr@xxxxxx> > Date: Sun, 06 Mar 2011 16:55:33 -0600 > >> Would it be safe enough to initialize code to SEGV_MAPERR earlier, or >> should vmalloc_fault have a different fault code? > > Yep, and that's how I'll fix this, thanks! > > --- > 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@xxxxxx> > Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx> > --- Thanks, no errors during compile. Tested-by: Bob Breuer <breuerr@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
