From: David Ahern <david.ahern@xxxxxxxxxx> Date: Tue, 31 Mar 2015 17:52:53 -0600 > On 3/31/15 5:38 PM, David Miller wrote: >> What is different in the PowerPC fault path vs. the Sparc one that >> causes the SIGBUS for sparc where the PowerPC does not see it? >> >> I don't understand where the SIGBUS comes from. In a pagefault >> disable section on sparc, in_atomic() should be true, thus we'll call >> do_kernel_fault(), fall through to the TSTATE_PRIV code path and >> simply run the exception handler. >> > > That's what I was hoping someone could explain to me. I'll dig deeper > on Monday. I've looked a few times at this and can't figure out what might be going wrong just from visual inspection. I'll try reproducing the problem and adding some diagnostics. -- 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