On 8/22/22 11:01, Sachin Sant wrote:
On 19-Aug-2022, at 10:12 AM, Ganesh wrote
We'll have to make sure everything get_pseries_errorlog() is either
forced inline, or marked noinstr.
Making the following functions always_inline and noinstr is fixing the issue.
__always_inline pseries_errorlo
On 8/22/22 11:19, Michael Ellerman wrote:
So I guess the compiler has decided not to inline it (why?!), and it is
not marked noinstr, so it gets KASAN instrumentation which crashes in
real mode.
We'll have to make sure everything get_pseries_errorlog() is either
forced inline, or marked noinstr
Ganesh writes:
> On 8/17/22 11:28, Michael Ellerman wrote:
>
>> Sachin Sant writes:
>>> Following crash is seen while running powerpc/mce subtest on
>>> a Power10 LPAR.
>>>
>>> 1..1
>>> # selftests: powerpc/mce: inject-ra-err
>>> [ 155.240591] BUG: Unable to handle kernel data access on read at
> On 19-Aug-2022, at 10:12 AM, Ganesh wrote
>>
>> We'll have to make sure everything get_pseries_errorlog() is either
>> forced inline, or marked noinstr.
>>
> Making the following functions always_inline and noinstr is fixing the issue.
> __always_inline pseries_errorlog_id()
> __always_inli
On 8/17/22 11:28, Michael Ellerman wrote:
Sachin Sant writes:
Following crash is seen while running powerpc/mce subtest on
a Power10 LPAR.
1..1
# selftests: powerpc/mce: inject-ra-err
[ 155.240591] BUG: Unable to handle kernel data access on read at
0xc00e00022d55b503
[ 155.240618] Faultin
Sachin Sant writes:
> Following crash is seen while running powerpc/mce subtest on
> a Power10 LPAR.
>
> 1..1
> # selftests: powerpc/mce: inject-ra-err
> [ 155.240591] BUG: Unable to handle kernel data access on read at
> 0xc00e00022d55b503
> [ 155.240618] Faulting instruction address: 0xc
Following crash is seen while running powerpc/mce subtest on
a Power10 LPAR.
1..1
# selftests: powerpc/mce: inject-ra-err
[ 155.240591] BUG: Unable to handle kernel data access on read at
0xc00e00022d55b503
[ 155.240618] Faulting instruction address: 0xc06f1f0c
[ 155.240627] Oops: Ker
