lkml.org 
[lkml]   [2008]   [Apr]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110
On Mon, 14 Apr 2008 00:44:22 +0400 Alexey Dobriyan <adobriyan@gmail.com> wrote:

> Grrr, I was hunting for oopses in dup_fd and near that were plaguing one
> box here for far too long, and hit below.
>
> What happened if freshly booted box (probably not all init scripts finished),
> X already started. ssh from another box and reboot from session.
>
>
> (gdb) p __kmalloc
> $1 = {void *(size_t, gfp_t)} 0xffffffff80286890 <__kmalloc>
> (gdb) l *(0xffffffff80286890 + 0x69)
> 0xffffffff802868f9 is in __kmalloc (mm/slub.c:1663).
> 1658
> 1659 object = __slab_alloc(s, gfpflags, node, addr, c);
> 1660
> 1661 else {
> 1662 object = c->freelist;
> 1663 ===> c->freelist = object[c->offset]; <===
> 1664 stat(c, ALLOC_FASTPATH);
> 1665 }
> 1666 local_irq_restore(flags);

Yes, I don't think the sub changes are ready for prime-time.

There is a fix in
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc8/2.6.25-rc8-mm2/hot-fixes
but it won't help this crash.


\
 
 \ /
  Last update: 2008-04-13 22:57    [W:0.244 / U:0.688 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site