From: Wu Jian Feng <jianfengw@mobilesoft.com.cn>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
linux-mtd@lists.infradead.org,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.6.8-rc3 slab corruption (jffs2?)
Date: Tue, 10 Aug 2004 08:52:04 +0800 [thread overview]
Message-ID: <20040810005204.GA15714@mobilesoft.com.cn> (raw)
In-Reply-To: <1092057472.4383.5155.camel@hades.cambridge.redhat.com>
On Mon, Aug 09, 2004 at 02:17:53PM +0100, David Woodhouse wrote:
>
> Please could you test this....
>
It doesn't compile :-(
--- mtdpart.c.old 2004-08-10 08:47:22.000000000 +0800
+++ mtdpart.c 2004-08-10 00:39:11.000000000 +0800
@@ -252,7 +252,7 @@
void mtd_erase_callback(struct erase_info *instr)
{
if (instr->mtd->erase == part_erase) {
- struct mtd_part *part = PART(mtd);
+ struct mtd_part *part = PART(instr->mtd);
if (instr->fail_addr != 0xffffffff)
instr->fail_addr -= part->offset;
Then worked fine here, Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Wu Jian Feng <jianfengw@mobilesoft.com.cn>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Wu Jian Feng <jianfengw@mobilesoft.com.cn>,
Russell King <rmk+lkml@arm.linux.org.uk>,
linux-mtd@lists.infradead.org,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.6.8-rc3 slab corruption (jffs2?)
Date: Tue, 10 Aug 2004 08:52:04 +0800 [thread overview]
Message-ID: <20040810005204.GA15714@mobilesoft.com.cn> (raw)
In-Reply-To: <1092057472.4383.5155.camel@hades.cambridge.redhat.com>
On Mon, Aug 09, 2004 at 02:17:53PM +0100, David Woodhouse wrote:
>
> Please could you test this....
>
It doesn't compile :-(
--- mtdpart.c.old 2004-08-10 08:47:22.000000000 +0800
+++ mtdpart.c 2004-08-10 00:39:11.000000000 +0800
@@ -252,7 +252,7 @@
void mtd_erase_callback(struct erase_info *instr)
{
if (instr->mtd->erase == part_erase) {
- struct mtd_part *part = PART(mtd);
+ struct mtd_part *part = PART(instr->mtd);
if (instr->fail_addr != 0xffffffff)
instr->fail_addr -= part->offset;
Then worked fine here, Thanks!
next prev parent reply other threads:[~2004-08-10 0:47 UTC|newest]
Thread overview: 18+ 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 14:04 ` Russell King
2004-08-07 21:59 ` David Woodhouse
2004-08-07 21:59 ` David Woodhouse
2004-08-08 6:12 ` Wu Jian Feng
2004-08-08 10:53 ` David Woodhouse
2004-08-08 10:53 ` David Woodhouse
2004-08-09 1:59 ` Wu Jian Feng
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
2004-08-09 13:17 ` David Woodhouse
2004-08-10 0:52 ` Wu Jian Feng [this message]
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=20040810005204.GA15714@mobilesoft.com.cn \
--to=jianfengw@mobilesoft.com.cn \
--cc=dwmw2@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.