Messages in this thread | | | Date | Mon, 25 Aug 2008 20:14:52 +0200 | From | "Vegard Nossum" <> | Subject | Re: Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected |
| |
On Tue, Aug 19, 2008 at 9:46 PM, Andrew Morton <akpm@linux-foundation.org> 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.
Hm.
Config doesn't even have CONFIG_PREEMPT, so preempt_disable() should be a no-op.
Vegard
-- "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
| |