public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: Linux kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kyle McMartin <kyle@redhat.com>
Subject: SLUB BUG: check_slab called with interrupts enabled
Date: Wed, 15 Jun 2011 10:56:15 -0400	[thread overview]
Message-ID: <4DF8C80F.7090403@redhat.com> (raw)

Hi Christoph,

last night I got an interesting backtrace running 3.0-rc3
(Fedora Rawhide kernel package).  Unfortunately netconsole
seems to be incompatible with KVM at the moment, so I had
to capture the oops on my digital camera and will be
transcribing just the backtrace.

Essentially, kernel 3.0-rc3 hit this bug:

static int check_slab(struct kmem_cache *s, struct page *page)
{
         int maxobj;

         VM_BUG_ON(!irqs_disabled());

The call trace:

check_slab
alloc_debug_processing
__slab_alloc
kmem_cache_alloc
bvec_alloc_bs
bio_alloc_bioset
bio_alloc
mpage_alloc
do_mpage_readpage
... followed by ext4 and VFS code, obviously innocent


Is this a known issue, Christoph?

If not, anything I can do to help debug/fix this?

-- 
All rights reversed

             reply	other threads:[~2011-06-15 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 14:56 Rik van Riel [this message]
2011-06-15 15:03 ` SLUB BUG: check_slab called with interrupts enabled Christoph Lameter
2011-06-15 15:16   ` Rik van Riel
2011-06-15 15:45     ` Christoph Lameter
2011-06-15 16:24       ` Rik van Riel
2011-06-16 12:34       ` Rik van Riel
2011-06-16 15:57         ` Christoph Lameter
2011-06-17  0:22           ` Rik van Riel

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=4DF8C80F.7090403@redhat.com \
    --to=riel@redhat.com \
    --cc=cl@linux.com \
    --cc=kyle@redhat.com \
    --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