From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Alan D. Brunelle" <Alan.Brunelle@hp.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected
Date: Mon, 25 Aug 2008 20:14:52 +0200 [thread overview]
Message-ID: <19f34abd0808251114p7b03b21oeb865b1706e095ef@mail.gmail.com> (raw)
In-Reply-To: <20080819124602.9e8e69f7.akpm@linux-foundation.org>
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
prev parent reply other threads:[~2008-08-25 18:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 23:03 Alan D. Brunelle
2008-08-13 23:27 ` Alan D. Brunelle
2008-08-14 16:14 ` Rafael J. Wysocki
2008-08-14 19:21 ` Alan D. Brunelle
2008-08-14 20:29 ` Rafael J. Wysocki
2008-08-19 19:46 ` Andrew Morton
2008-08-22 15:37 ` Alan D. Brunelle
2008-08-22 16:25 ` Andrew Morton
2008-08-22 17:16 ` Petr Baudis
2008-08-22 17:51 ` Andrew Morton
2008-08-22 18:07 ` Alan D. Brunelle
2008-08-22 19:37 ` Björn Steinbrink
2008-08-22 19:47 ` Alan D. Brunelle
2008-08-22 20:17 ` Alan D. Brunelle
2008-08-22 19:48 ` Jeff King
2008-08-22 21:05 ` Junio C Hamano
2008-08-22 21:16 ` Andrew Morton
2008-08-22 21:21 ` Jeff King
2008-08-22 21:36 ` Björn Steinbrink
2008-08-25 18:14 ` Vegard Nossum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0808251114p7b03b21oeb865b1706e095ef@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=Alan.Brunelle@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®