Re: [PATCH 11/13] powerpc/64s: Save r13 in machine_check_common_early

2019-06-22 Thread Reza Arbab
On Sat, Jun 22, 2019 at 09:21:55AM +1000, Nicholas Piggin wrote: Yep, from the stack trace, r13 is corrupted. So r13 must have got corrupted before the machine check and this just happens to have corrected it. How does cause_ue work? It or memcpy_mcsafe must be corrupting r13. Well, cause_ue()

Re: [PATCH 11/13] powerpc/64s: Save r13 in machine_check_common_early

2019-06-21 Thread Nicholas Piggin
Mahesh J Salgaonkar's on June 21, 2019 9:47 pm: > On 2019-06-21 06:27:15 Fri, Santosh Sivaraj wrote: >> From: Reza Arbab >> >> Testing my memcpy_mcsafe() work in progress with an injected UE, I get >> an error like this immediately after the function returns: >> >> BUG: Unable to handle kernel d

Re: [PATCH 11/13] powerpc/64s: Save r13 in machine_check_common_early

2019-06-21 Thread Mahesh J Salgaonkar
On 2019-06-21 06:27:15 Fri, Santosh Sivaraj wrote: > From: Reza Arbab > > Testing my memcpy_mcsafe() work in progress with an injected UE, I get > an error like this immediately after the function returns: > > BUG: Unable to handle kernel data access at 0x7fff84dec8f8 > Faulting instruction addr

[PATCH 11/13] powerpc/64s: Save r13 in machine_check_common_early

2019-06-20 Thread Santosh Sivaraj
From: Reza Arbab Testing my memcpy_mcsafe() work in progress with an injected UE, I get an error like this immediately after the function returns: BUG: Unable to handle kernel data access at 0x7fff84dec8f8 Faulting instruction address: 0xc008009c00b0 Oops: Kernel access of bad area, sig: 11