From: Artem Bityutskiy <dedekind@infradead.org>
To: Vijay Kumar <vijaykumar@bravegnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NAND: nandsim bad block injection
Date: Tue, 02 Jan 2007 10:13:37 +0200 [thread overview]
Message-ID: <1167725617.20245.8.camel@sauron> (raw)
In-Reply-To: <17815.54197.666735.904351@vaishnavi.localdomain>
On Sun, 2006-12-31 at 20:43 +0530, Vijay Kumar wrote:
> Artem Bityutskiy writes:
> > 1. Suppose we decided to emulate an erase failure for a certain
> > eraseblock. Then the MTD user re-tries the operation and succeeds.
> > Shouldn't we start always returning erase errors for this eraseblock
> > instead?
>
> You are right. We should be mantaining the bad block state within the
> simulator. I will update the code accordingly.
Well, may be it is also useful to sporadically emulate errors which go
away after re-try.
> > 2. In case of I/O errors, the correct MTD user should mark the bogus
> > eraseblock bad. So, after some time we end up with most of our
> > eraseblocks marked bad which is not very nice.
> >
> > How would you comment this?
>
> We can have an upper limit on the no. of blocks that can turn bad. It
> can be provided as a module parameter.
Yeah.
Also, one more nice feature would be to emulate bit-flips from time to
time. Just change one bit and let NAND level to fix it using ECC. This
would be good for testing both NAND layer and applications (MTD returns
-EUCLEAN in case of a bit flip, and applications should not panic in
this case - because the bit-flip was corrected). That's just an idea.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
parent reply other threads:[~2007-01-02 8:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <17815.54197.666735.904351@vaishnavi.localdomain>]
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=1167725617.20245.8.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vijaykumar@bravegnu.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