All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: dedekind@infradead.org
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: NAND flash write goes wrong
Date: Fri, 11 May 2007 09:16:09 +0200	[thread overview]
Message-ID: <46441839.2020004@parrot.com> (raw)
In-Reply-To: <1178866648.3643.7.camel@sauron>

Hi Artem,

Artem Bityutskiy a écrit :
> Just FYI,
> 
> we have recently fixed a bug in MTD which caused JFFS2 to mark good
> eraseblocks bad. It was caused by the mtdpart module. One had to have
> partitions to trigger this bug. The bug was that when JFFS2 wanted to
> mark eraseblock X within its partition as bad, mtdpart did not translate
> correctly to the _absolute_ number, but marked _absolute_ eraseblock
> number X as bad instead.
> 
> So basically, once one met a true bad eraseblock, JFFS2 started trying
> to mark it as bad, but marked other eraseblock as bad instead.
> 
> I'd recommend everybody to backport this fix.
> 
Could you give a link to your fix ?


Thanks

Matthieu

  reply	other threads:[~2007-05-11  7:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 18:50 NAND flash write goes wrong borasah
2007-05-10 19:16 ` Josh Boyer
2007-05-10 21:37   ` borasah
2007-05-10 22:15     ` Thomas Gleixner
2007-05-10 22:42       ` borasah
2007-05-11  6:36 ` Ricard Wanderlof
2007-05-11  6:57   ` Artem Bityutskiy
2007-05-11  7:16     ` Matthieu CASTET [this message]
2007-05-11  7:42       ` Artem Bityutskiy
2007-05-11  7:49         ` Artem Bityutskiy
2007-05-11 13:56   ` borasah
2007-05-11 14:31     ` Ricard Wanderlof
2007-05-11 17:58       ` borasah
2007-05-14  6:56         ` Ricard Wanderlof
2007-05-21  9:30           ` borasah
     [not found] <42E999AD7A0E4647BF159F467EE4FBCB017B5155@BLR-SGM-MSG01.wipro.com>
2007-05-14  7:39 ` Ricard Wanderlof

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=46441839.2020004@parrot.com \
    --to=matthieu.castet@parrot.com \
    --cc=dedekind@infradead.org \
    --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 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.