lkml.org 
[lkml]   [2012]   [Oct]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kernel null pointer dereference at kmem_cache_alloc+0x5b/0x140
On Tue, 2 Oct 2012, Shuah Khan wrote:
> I started seeing the following null pointer dereference on
> a linux-next sept 21 git and still seeing it on linux-next
> Sep 27th git.
>
> Can be reproduced easily. I have been able to reproduce every
> time I do a complete build of a kernel on fresh checkout or
> touch a header file that forces full build.
>
> I didn't get a chance to investigate this yet, thought I would
> share just in case others have seen it.
>
> [11478.881196] BUG: unable to handle kernel NULL pointer dereference at 0000000000000001
> [11478.881245] IP: [<ffffffff811742bb>] kmem_cache_alloc+0x5b/0x140
> [11478.881277] PGD 74386067 PUD 5dfab067 PMD 0
> [11478.881302] Oops: 0000 [#2] SMP
> [11478.881705] CPU 0
> [11478.881717] Pid: 6399, comm: ld Tainted: G D 3.6.0-rc7-next-20120927+ #1 Hewlett-Packard HP EliteBook 6930p/30DC
> [11478.884005] Process ld (pid: 6399, threadinfo ffff88005dec0000, task ffff88007bf244a0)
> [11478.884005] Call Trace:
> [11478.884005] [<ffffffff8125dab1>] ext4_es_insert_extent+0x1e1/0x2f0

ext4_es_insert_extent again: probably fixed by the same patch as I just
sent in your other kernel NULL pointer dereference thread.

Hugh


\
 
 \ /
  Last update: 2012-10-02 23:21    [W:0.159 / U:0.748 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site