public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Nahor <nahor.j+gmane@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Nandwrite's behavior in case of write failure
Date: Thu, 04 Jun 2009 18:23:39 -0700	[thread overview]
Message-ID: <h09s2s$ar6$1@ger.gmane.org> (raw)

Hi,

If the call to pwrite fails, nanwrite tries first to erase the block 
then to mark it as bad. If erase fails, nandwrite aborts. If setting the 
bad block flag fails, nandwrite just ignores it and go to the next block.

My questions are:
- Why erase the block?
- Probably linked to the first question, why abort if erase fails? Why 
not just ignore it and rely on the bad block flag?
- Why ignore the bad block flag error? If nandwrite can't set it and 
just goes on, the caller (app ou user) will think that everything is 
good. But when reading the partition later, the user will garbage when 
reaching that page.


Thanks,
	Nahor

             reply	other threads:[~2009-06-05  1:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05  1:23 Nahor [this message]
2009-06-05 12:31 ` Nandwrite's behavior in case of write failure Artem Bityutskiy
2009-06-06  2:40   ` Nahor
2009-06-07  8:57     ` Artem Bityutskiy
2009-06-08 17:00       ` Nahor
2009-06-08 20:43       ` Jehan Bing
2009-06-09 12:59         ` Artem Bityutskiy

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='h09s2s$ar6$1@ger.gmane.org' \
    --to=nahor.j+gmane@gmail.com \
    --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