On Thursday, February 7, 2019 5:27:09 AM IST Michael Ellerman wrote:
> Chandan Rajendra writes:
> > On Wednesday, February 6, 2019 5:20:04 PM IST Michael Ellerman wrote:
> >> Chandan Rajendra writes:
> >> > On Friday, February 1, 2019 4:43:52 PM IST Michael Ellerman wrote:
> >> >> Michael
Chandan Rajendra writes:
> On Wednesday, February 6, 2019 5:20:04 PM IST Michael Ellerman wrote:
>> Chandan Rajendra writes:
>> > On Friday, February 1, 2019 4:43:52 PM IST Michael Ellerman wrote:
>> >> Michael Ellerman writes:
>> >>
>> >> > Adding Simon who wrote the code.
>> >> >
>> >> >
On Wednesday, February 6, 2019 5:20:04 PM IST Michael Ellerman wrote:
> Chandan Rajendra writes:
> > On Friday, February 1, 2019 4:43:52 PM IST Michael Ellerman wrote:
> >> Michael Ellerman writes:
> >>
> >> > Adding Simon who wrote the code.
> >> >
> >> > Chandan Rajendra writes:
> >> >> When
Chandan Rajendra writes:
> On Friday, February 1, 2019 4:43:52 PM IST Michael Ellerman wrote:
>> Michael Ellerman writes:
>>
>> > Adding Simon who wrote the code.
>> >
>> > Chandan Rajendra writes:
>> >> When executing fstests' generic/026 test, I hit the following call trace,
>> >>
>> >> [
On Friday, February 1, 2019 4:43:52 PM IST Michael Ellerman wrote:
> Michael Ellerman writes:
>
> > Adding Simon who wrote the code.
> >
> > Chandan Rajendra writes:
> >> When executing fstests' generic/026 test, I hit the following call trace,
> >>
> >> [ 417.061038] BUG: Unable to handle
Michael Ellerman writes:
> Adding Simon who wrote the code.
>
> Chandan Rajendra writes:
>> When executing fstests' generic/026 test, I hit the following call trace,
>>
>> [ 417.061038] BUG: Unable to handle kernel data access at 0xc0062ac4
>> [ 417.062172] Faulting instruction
Adding Simon who wrote the code.
Chandan Rajendra writes:
> When executing fstests' generic/026 test, I hit the following call trace,
>
> [ 417.061038] BUG: Unable to handle kernel data access at 0xc0062ac4
> [ 417.062172] Faulting instruction address: 0xc0092240
> [
Le 25/01/2019 à 01:55, Benjamin Herrenschmidt a écrit :
On Thu, 2019-01-24 at 19:48 +0530, Chandan Rajendra wrote:
- Here we execute "LD rB,0,r4". In the case of this bug, r4 has an unaligned
value and hence ends up accessing the "next" double word. The "next" double
word happens to
On Thu, 2019-01-24 at 19:48 +0530, Chandan Rajendra wrote:
> - Here we execute "LD rB,0,r4". In the case of this bug, r4 has an unaligned
> value and hence ends up accessing the "next" double word. The "next" double
> word happens to occur after the last page mapped into the kernel's address
>
When executing fstests' generic/026 test, I hit the following call trace,
[ 417.061038] BUG: Unable to handle kernel data access at 0xc0062ac4
[ 417.062172] Faulting instruction address: 0xc0092240
[ 417.062242] Oops: Kernel access of bad area, sig: 11 [#1]
[ 417.062299] LE
10 matches
Mail list logo