public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandru DAMIAN <ddalex@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG message while using jffs2
Date: Sat, 10 Nov 2007 10:37:17 +0200	[thread overview]
Message-ID: <1194683837.5688.4.camel@localhost> (raw)
In-Reply-To: <1194647963.2588.41.camel@shinybook.infradead.org>

I'm running stock kernel on a Fedora 7. uname -a tells 

Linux sandel.gameloft.org 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT
2007 i686 i686 i386 GNU/Linux

In the stock 2.6.22.9 kernel, I see a bugon on slub.c, the code is this:

2196 static struct kmem_cache *get_slab(size_t size, gfp_t flags)
2197 {
2198         int index = kmalloc_index(size);
2199 
2200         if (!index)
2201                 return NULL;
2202 
2203         /* Allocation too large? */
2204         BUG_ON(index < 0);

Hope this helps,

Cheers,
Alex

On Fri, 2007-11-09 at 17:39 -0500, David Woodhouse wrote:
> On Fri, 2007-11-09 at 17:08 +0200, Alexandru Damian wrote:
> > Hello,
> > 
> > Sorry for posting here, it seems the best spot; if I need to redirect
> > this to mtd-utils team, please tell me.
> > 
> > I'm playing around with some jffs2 files. While trying to mount (via
> > block2mtd, loop) a jffs2 system, a "kernel BUG message" appeared in
> > dmesg, with these lines:
> > 
> > kernel BUG at mm/slub.c:2204!
> 
> I don't see a BUG() or BUG_ON() anywhere near that line. What version of
> the kernel? Precisely what is at that line?
> 


      reply	other threads:[~2007-11-10  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 15:08 kernel BUG message while using jffs2 Alexandru Damian
2007-11-09 22:39 ` David Woodhouse
2007-11-10  8:37   ` Alexandru DAMIAN [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=1194683837.5688.4.camel@localhost \
    --to=ddalex@gmail.com \
    --cc=dwmw2@infradead.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