From: Wu Jian Feng <jianfengw@mobilesoft.com.cn>
To: Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org
Cc: Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [BUG] 2.6.8-rc3 slab corruption (jffs2?)
Date: Sun, 8 Aug 2004 14:12:06 +0800 [thread overview]
Message-ID: <20040808061206.GA5417@mobilesoft.com.cn> (raw)
In-Reply-To: <20040807150458.E2805@flint.arm.linux.org.uk>
Can't figure out why but have a quick workaround for this:
--- a/fs/jffs2/erase.c 2004-08-08 14:03:06.000000000 +0800
+++ b/fs/jffs2/erase.c 2004-08-08 14:05:41.000000000 +0800
@@ -72,8 +72,10 @@
((struct erase_priv_struct *)instr->priv)->c = c;
ret = c->mtd->erase(c->mtd, instr);
- if (!ret)
+ if (!ret) {
+ kfree(instr);
return;
+ }
bad_offset = instr->fail_addr;
kfree(instr);
@@ -206,7 +208,6 @@
} else {
jffs2_erase_succeeded(priv->c, priv->jeb);
}
- kfree(instr);
}
#endif /* !__ECOS */
On Sat, Aug 07, 2004 at 03:04:58PM +0100, Russell King wrote:
> Not sure exactly what caused this, but it happened while logging in
> (after fixing the previous two reported problems - the first by backing
> out the last change to redboot.c and the second by commenting out
> ri->usercompr in fs/jffs2/read.c.)
>
> Slab corruption: start=c1e39474, len=64
> Redzone: 0x5a2cf071/0x5a2cf071.
> Last user: [<c032ca10>](cfi_intelext_erase_varsize+0x58/0x64)
> 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 4f 6b
> Prev obj: start=c1e39428, len=64
> Redzone: 0x5a2cf071/0x5a2cf071.
> Last user: [<c02c767c>](jffs2_garbage_collect_deletion_dirent+0x80/0x8c)
> 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=c1e394c0, len=64
> Redzone: 0x170fc2a5/0x170fc2a5.
> Last user: [<c03514f8>](neigh_hh_init+0x64/0x11c)
> 000: 00 00 00 00 03 00 00 00 08 00 00 00 0e 00 00 00
> 010: 00 b0 34 c0 00 00 08 00 2b 95 1d 7b 00 c0 1b 00
>
> Due to tail call optimisation, its difficult to work out exactly what's
> going on, but the first seems to be a kfree call from the erase callback
> (possibly jffs2_erase_callback). The second function is the call to
> jffs2_free_full_dirent() in jffs2_garbage_collect_deletion_dirent().
>
> Any ideas? I haven't been able to reproduce (presumably because the
> erase succeeded, and we didn't need to re-erase again.)
>
> --
> Russell King
> Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
> maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
> 2.6 Serial core
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2004-08-08 6:07 UTC|newest]
Thread overview: 12+ 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
2004-08-08 6:12 ` Wu Jian Feng [this message]
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:17 ` David Woodhouse
2004-08-10 0:52 ` Wu Jian Feng
2004-08-10 13:16 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-08-08 9:23 Manfred Spraul
2004-08-08 9:36 ` Russell King
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=20040808061206.GA5417@mobilesoft.com.cn \
--to=jianfengw@mobilesoft.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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