ha Levin wrote:
> >>>> >Hi all,
> >>>> >
> >>>> >While fuzzing with trinity inside a KVM tools guest running latest -next
> >>>> >kernel I've stumbled on the following (now with pretty line numbers!)
> >>>> >s
with trinity inside a KVM tools guest running latest -next
kernel I've stumbled on the following (now with pretty line numbers!)
spew:
[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
It VM_BUG_ON_PAGE(!PageHead(page), page);, correct?
I don't see dump_page() output.
Right. However
>While fuzzing with trinity inside a KVM tools guest running latest -next
>>>> >kernel I've stumbled on the following (now with pretty line numbers!)
>>>> >spew:
>>>> >
>>>> >[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
>>
stumbled on the following (now with pretty line numbers!)
spew:
[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
It VM_BUG_ON_PAGE(!PageHead(page), page);, correct?
I don't see dump_page() output.
Right. However, I'm not seeing the dump_page() output in the log.
I see that dump_page
with pretty line numbers!) spew:
>
>[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
It "VM_BUG_ON_PAGE(!PageHead(page), page);", correct?
I don't see dump_page() output.
Right. However, I'm not seeing the dump_page() output in the log.
I see that dump_page() has been modifi
line numbers!) spew:
[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
It VM_BUG_ON_PAGE(!PageHead(page), page);, correct?
I don't see dump_page() output.
Right. However, I'm not seeing the dump_page() output in the log.
I see that dump_page() has been modified not long ago, I'm looking
>[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
It "VM_BUG_ON_PAGE(!PageHead(page), page);", correct?
I don't see dump_page() output.
Right. However, I'm not seeing the dump_page() output in the log.
I see that dump_page() has been modified not long ago, I'm looking into it.
Than
On Fri, Feb 21, 2014 at 05:46:36PM -0500, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel I've stumbled on the following (now with pretty line numbers!) spew:
>
> [ 746.125099] kernel BUG at mm/
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next kernel I've stumbled on the
following (now with pretty line numbers!) spew:
[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
[ 746.125775] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 746.126774
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next kernel I've stumbled on the
following (now with pretty line numbers!) spew:
[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
[ 746.125775] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 746.126774
On Fri, Feb 21, 2014 at 05:46:36PM -0500, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel I've stumbled on the following (now with pretty line numbers!) spew:
[ 746.125099] kernel BUG at mm/huge_memory.c:1371!
It VM_BUG_ON_PAGE
at mm/huge_memory.c:1371!
It VM_BUG_ON_PAGE(!PageHead(page), page);, correct?
I don't see dump_page() output.
Right. However, I'm not seeing the dump_page() output in the log.
I see that dump_page() has been modified not long ago, I'm looking into it.
Thanks,
Sasha
--
To unsubscribe from
12 matches
Mail list logo