On 06/17/2014 11:36 PM, Hugh Dickins wrote:
> On Mon, 16 Jun 2014, Sasha Levin wrote:
>> On 06/10/2014 12:20 AM, Hugh Dickins wrote:
>>> Although there's nothing in the backtrace to implicate it,
>>> I think this crash is caused by THP: please try this patch - thanks.
>>>
>>> [PATCH] mm: let mm_fin
On Mon, 16 Jun 2014, Sasha Levin wrote:
> On 06/10/2014 12:20 AM, Hugh Dickins wrote:
> > Although there's nothing in the backtrace to implicate it,
> > I think this crash is caused by THP: please try this patch - thanks.
> >
> > [PATCH] mm: let mm_find_pmd fix buggy race with THP fault
...
>
> I
On Mon, 16 Jun 2014, Sasha Levin wrote:
> It took some time to hit something here, but I think that the following
> is related:
This related thing looks like someone did a random memset. The SLUB
diagnostic show the object, redzone and padding were overwritten with
zeros.
> [ 494.710068]
> ===
On 06/10/2014 12:20 AM, Hugh Dickins wrote:
> On Tue, 27 May 2014, Sasha Levin wrote:
>> > On 05/26/2014 04:05 PM, Hugh Dickins wrote:
>>> > > On Fri, 23 May 2014, Sasha Levin wrote:
>>> > >
> >> Ping?
> >>
> >> On 05/05/2014 11:51 AM, Sasha Levin wrote:
> > >>> Did anyone have
On Mon, Jun 09, 2014 at 09:20:33PM -0700, Hugh Dickins wrote:
> [PATCH] mm: let mm_find_pmd fix buggy race with THP fault
>
> Trinity has reported:
> BUG: unable to handle kernel NULL pointer dereference at 0018
> IP: __lock_acquire (kernel/locking/lockdep.c:3070 (discriminator 1))
> C
On Tue, 27 May 2014, Sasha Levin wrote:
> On 05/26/2014 04:05 PM, Hugh Dickins wrote:
> > On Fri, 23 May 2014, Sasha Levin wrote:
> >
> >> Ping?
> >>
> >> On 05/05/2014 11:51 AM, Sasha Levin wrote:
> >>> Did anyone have a chance to look at it? I still see it in -next.
> >>>
> >>>
> >>> Thanks,
> >
On 05/26/2014 04:05 PM, Hugh Dickins wrote:
> On Fri, 23 May 2014, Sasha Levin wrote:
>
>> Ping?
>>
>> On 05/05/2014 11:51 AM, Sasha Levin wrote:
>>> Did anyone have a chance to look at it? I still see it in -next.
>>>
>>>
>>> Thanks,
>>> Sasha
>>>
>>> On 04/16/2014 10:59 AM, Sasha Levin wrote:
>>
On Fri, 23 May 2014, Sasha Levin wrote:
> Ping?
>
> On 05/05/2014 11:51 AM, Sasha Levin wrote:
> > Did anyone have a chance to look at it? I still see it in -next.
> >
> >
> > Thanks,
> > Sasha
> >
> > On 04/16/2014 10:59 AM, Sasha Levin wrote:
> >> Hi all,
> >>
> >> While fuzzing with trinity
Ping?
On 05/05/2014 11:51 AM, Sasha Levin wrote:
> Did anyone have a chance to look at it? I still see it in -next.
>
>
> Thanks,
> Sasha
>
> On 04/16/2014 10:59 AM, Sasha Levin wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest running latest -next
>> kernel I've stumb
Did anyone have a chance to look at it? I still see it in -next.
Thanks,
Sasha
On 04/16/2014 10:59 AM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel I've stumbled on the following:
>
> [ 2552.313602] BUG: unable to handle ker
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel I've stumbled on the following:
[ 2552.313602] BUG: unable to handle kernel NULL pointer dereference at
0018
[ 2552.315878] IP: __lock_acquire (kernel/locking/lockdep.c:3070 (discriminator
1))
[
11 matches
Mail list logo