On 03/13/2014 04:57 PM, Hugh Dickins wrote:
On Thu, 13 Mar 2014, Davidlohr Bueso wrote:
On Tue, 2014-03-11 at 18:20 -0400, Sasha Levin wrote:
On 03/11/2014 05:45 PM, Davidlohr Bueso wrote:
On Tue, 2014-03-11 at 17:02 -0400, Sasha Levin wrote:
On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
Bi
On Thu, 13 Mar 2014, Davidlohr Bueso wrote:
> On Tue, 2014-03-11 at 18:20 -0400, Sasha Levin wrote:
> > On 03/11/2014 05:45 PM, Davidlohr Bueso wrote:
> > > On Tue, 2014-03-11 at 17:02 -0400, Sasha Levin wrote:
> > >> >On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
> > > >>Bingo! With the abov
On Tue, 2014-03-11 at 18:20 -0400, Sasha Levin wrote:
> On 03/11/2014 05:45 PM, Davidlohr Bueso wrote:
> > On Tue, 2014-03-11 at 17:02 -0400, Sasha Levin wrote:
> >> >On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
> > >>Bingo! With the above patch:
> > > >> >
> > > >> >[ 243.565794] k
On 03/11/2014 05:45 PM, Davidlohr Bueso wrote:
On Tue, 2014-03-11 at 17:02 -0400, Sasha Levin wrote:
>On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
> >>Bingo! With the above patch:
> >> >
> >> >[ 243.565794] kernel BUG at mm/vmacache.c:76!
> >> >[ 243.566720] invalid opcode: [#1] PREEM
On Tue, Mar 11, 2014 at 01:47:24PM -0700, Davidlohr Bueso wrote:
> On Tue, 2014-03-11 at 16:45 -0400, Sasha Levin wrote:
> > On 03/11/2014 04:30 PM, Andrew Morton wrote:
> > > All I can think is that find_vma() went and returned a vma from a
> > > different mm, which would be odd. How about I
On Tue, Mar 11, 2014 at 1:07 PM, Davidlohr Bueso wrote:
> On Tue, 2014-03-11 at 15:39 -0400, Sasha Levin wrote:
>> I've ended up deleting the log file by mistake, but this bug does seem to be
>> important
>> so I'd rather not wait before the same issue is triggered again.
>>
>> The call chain is
On Tue, 2014-03-11 at 17:02 -0400, Sasha Levin wrote:
> On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
> >> Bingo! With the above patch:
> >> >
> >> >[ 243.565794] kernel BUG at mm/vmacache.c:76!
> >> >[ 243.566720] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
> >> >[ 243.568048] Dumpin
On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
Bingo! With the above patch:
>
>[ 243.565794] kernel BUG at mm/vmacache.c:76!
>[ 243.566720] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
>[ 243.568048] Dumping ftrace buffer:
>[ 243.568740](ftrace buffer empty)
>[ 243.569481] Modul
On Tue, 2014-03-11 at 16:45 -0400, Sasha Levin wrote:
> On 03/11/2014 04:30 PM, Andrew Morton wrote:
> > All I can think is that find_vma() went and returned a vma from a
> > different mm, which would be odd. How about I toss this in there?
> >
> > --- a/mm/vmacache.c~a
> > +++ a/mm/vmacache.c
> >
On 03/11/2014 04:30 PM, Andrew Morton wrote:
All I can think is that find_vma() went and returned a vma from a
different mm, which would be odd. How about I toss this in there?
--- a/mm/vmacache.c~a
+++ a/mm/vmacache.c
@@ -72,8 +72,10 @@ struct vm_area_struct *vmacache_find(str
for (i =
On Tue, 2014-03-11 at 13:30 -0700, Andrew Morton wrote:
> On Tue, 11 Mar 2014 13:07:33 -0700 Davidlohr Bueso wrote:
>
> > On Tue, 2014-03-11 at 15:39 -0400, Sasha Levin wrote:
> > > Hi all,
> > >
> > > I've ended up deleting the log file by mistake, but this bug does seem to
> > > be important
On 03/11/2014 04:30 PM, Andrew Morton wrote:
I worry about what happens if __get_user_pages decides to do
if (ret & VM_FAULT_RETRY) {
if (nonblocking)
*nonblocking = 0;
On Tue, 11 Mar 2014 13:07:33 -0700 Davidlohr Bueso wrote:
> On Tue, 2014-03-11 at 15:39 -0400, Sasha Levin wrote:
> > Hi all,
> >
> > I've ended up deleting the log file by mistake, but this bug does seem to
> > be important
> > so I'd rather not wait before the same issue is triggered again.
>
On Tue, 2014-03-11 at 16:12 -0400, Sasha Levin wrote:
> On 03/11/2014 04:07 PM, Davidlohr Bueso wrote:
> > On Tue, 2014-03-11 at 15:39 -0400, Sasha Levin wrote:
> >> Hi all,
> >>
> >> I've ended up deleting the log file by mistake, but this bug does seem to
> >> be important
> >> so I'd rather not
On 03/11/2014 04:07 PM, Davidlohr Bueso wrote:
On Tue, 2014-03-11 at 15:39 -0400, Sasha Levin wrote:
Hi all,
I've ended up deleting the log file by mistake, but this bug does seem to be
important
so I'd rather not wait before the same issue is triggered again.
The call chain is:
mloc
On Tue, 2014-03-11 at 15:39 -0400, Sasha Levin wrote:
> Hi all,
>
> I've ended up deleting the log file by mistake, but this bug does seem to be
> important
> so I'd rather not wait before the same issue is triggered again.
>
> The call chain is:
>
> mlock (mm/mlock.c:745)
>
Hi all,
I've ended up deleting the log file by mistake, but this bug does seem to be
important
so I'd rather not wait before the same issue is triggered again.
The call chain is:
mlock (mm/mlock.c:745)
__mm_populate (mm/mlock.c:700)
__mlock_vma_p
17 matches
Mail list logo
