From: Jarkko Lavinen <jarkko.lavinen@nokia.com>
To: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Wu Jian Feng <jianfengw@mobilesoft.com.cn>
Subject: Re: [BUG] 2.6.8-rc3 slab corruption (jffs2?)
Date: Mon, 9 Aug 2004 16:11:59 +0300 [thread overview]
Message-ID: <20040809131158.GA6838@angel.research.nokia.com> (raw)
In-Reply-To: <1092049678.4383.5149.camel@hades.cambridge.redhat.com>
On Mon, Aug 09, 2004 at 12:07:59PM +0100, ext David Woodhouse wrote:
> Don't bother, thanks. I found the problem, in the part_erase() code.
> Waiting for the culprit to wake up and fix it... :)
I also see the Slab corruption and it is very reproducible with
something like:
flash_eraseall -j /dev/mtd0
mount -t jffs2 /dev/mtdblock0 /mnt
cp -a /usr /mnt
I am using Nand flash and 2.6.8-rc3-omap1. Once the fs is filled
enough I see typically following:
Slab corruption: start=c3a31980, len=64
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c0185fd0>](nand_erase_nand+0x1fc/0x210)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 09 6b
Prev obj: start=c3a31934, len=64
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<00000000>](0x0)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Next obj: start=c3a319cc, len=64
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<c00fcddc>](jffs2_alloc_full_dirent+0x18/0x1c)
000: 8c 68 80 c3 30 11 a3 c3 0d 00 00 00 a1 0c 00 00
010: 46 4d 28 9e 08 44 62 44 72 69 76 65 72 2e 70 6d
Jarkko Lavinen
next prev parent reply other threads:[~2004-08-09 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 14:04 [BUG] 2.6.8-rc3 slab corruption (jffs2?) Russell King
2004-08-07 21:59 ` David Woodhouse
[not found] ` <20040808061206.GA5417@mobilesoft.com.cn>
2004-08-08 10:53 ` David Woodhouse
2004-08-09 1:59 ` Wu Jian Feng
2004-08-09 6:41 ` David Woodhouse
2004-08-09 11:07 ` David Woodhouse
2004-08-09 13:11 ` Jarkko Lavinen [this message]
2004-08-09 13:17 ` David Woodhouse
2004-08-10 0:52 ` Wu Jian Feng
2004-08-10 13:16 ` David Woodhouse
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=20040809131158.GA6838@angel.research.nokia.com \
--to=jarkko.lavinen@nokia.com \
--cc=dwmw2@infradead.org \
--cc=jianfengw@mobilesoft.com.cn \
--cc=linux-mtd@lists.infradead.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