[lkml]   [2008]   [Aug]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected
On Tue, Aug 19, 2008 at 9:46 PM, Andrew Morton
<> wrote:
> Thing is, the code *isn't* in an interrupt. Something got screwed up.
> What can happen is that some code has a lock imbalance or a
> preempt_disable imbalance and it does preempt_disable() so many times
> that the counter overflows eight bits and starts to increment the
> softirq counter, then the hardirq counter, then in_interrupt() starts
> incorrectly returning true then blam.


Config doesn't even have CONFIG_PREEMPT, so preempt_disable() should be a no-op.


"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036

 \ /
  Last update: 2008-08-25 20:17    [W:0.112 / U:1.776 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site