public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sesterhenn <snakebyte@gmx.de>
To: linux-ext4@vger.kernel.org
Subject: Re: BUG_ON at mballoc.c:3752
Date: Thu, 31 Jan 2008 16:42:07 +0100	[thread overview]
Message-ID: <20080131154207.GA22201@alice> (raw)
In-Reply-To: <20080131140137.GA20780@alice>

* Eric Sesterhenn (snakebyte@gmx.de) wrote:
> hi,
> 
> while running a modified version of fsfuzzer i triggered the BUG() in
> ext4_mb_release_inode_pa(). Sadly I am not able to reproduce this using
> the generated image, but running the fuzzer will usually trigger this in
> less than 40 attempts. Increasing the JBD2 Debug level didnt give more
> information. The kernel is current git with
> ext4-fix-null-pointer-deref-in-journal_wait_on_commit_record.patch
> applied. 

I am now able to reproduce this using this image:
http://www.cccmz.de/~snakebyte/ext4.24.img.bz2

the following commands will trigger the oops for me

mount cfs/ext4.24.img /media/test -t ext4dev -o extents -o loop
mkdir /media/test/stress
chown snakebyte:snakebyte /media/test/stress && sudo -u snakebyte fstest -n 10 -l 10 -f 5 -s 40000 -p /media/test/stress/


The && between the chown and fstest seems necessary

Greetings, Eric

  reply	other threads:[~2008-01-31 15:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 14:01 BUG_ON at mballoc.c:3752 Eric Sesterhenn
2008-01-31 15:42 ` Eric Sesterhenn [this message]
2008-02-04  6:00   ` Aneesh Kumar K.V
2008-02-04  8:29     ` Eric Sesterhenn
2008-02-06 21:59     ` Dave Kleikamp
2008-02-07 12:55       ` Aneesh Kumar K.V
2008-02-08  1:30         ` Mingming Cao
2008-02-08  3:14           ` Aneesh Kumar K.V
2008-02-08  3:30             ` Eric Sandeen
2008-02-08 13:47         ` Eric Sesterhenn
2008-02-08 15:07         ` Eric Sesterhenn
2008-02-08 15:26           ` Eric Sandeen
2008-02-08 15:31             ` Eric Sesterhenn
2008-02-08 15:33               ` Eric Sandeen
2008-02-01 19:34 ` Mingming Cao

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=20080131154207.GA22201@alice \
    --to=snakebyte@gmx.de \
    --cc=linux-ext4@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