All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricard Wanderlof <ricard.wanderlof@axis.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Anton Olofsson <anol.martinsson@gmail.com>
Subject: Re: mtd-utils: ubiformat: writing images on flash with badblocks.
Date: Mon, 12 Sep 2011 08:41:55 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1109120840020.8150@lnxricardw.se.axis.com> (raw)
In-Reply-To: <1315738766.18731.9.camel@sauron>


> On Sun, 11 Sep 2011, Artem Bityutskiy wrote:
> 
> This issue was reported and analyzed by
> Anton Olofsson <anol.martinsson@gmail.com>:
> 
> when ubiformat encounters a write error while flashing the UBI image (which may
> come from a file of from stdout), it correctly marks the faulty eraseblock as
> bad and skips it. However, it also incorrectly drops the data buffer which was
> supposed to be written, and reads next block of data.

I'm just curious, how come this has gone unnoticed for so long? One would 
think that someone would have tried to flash an image to a chip with bad 
blocks a long time ago?

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30

  reply	other threads:[~2011-09-12  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  8:26 mtd-utils: ubiformat: writing images on flash with badblocks Anton Olofsson
2011-09-11 10:59 ` Artem Bityutskiy
2011-09-12  6:41   ` Ricard Wanderlof [this message]
2011-09-12  9:33     ` Artem Bityutskiy
2011-09-12  9:40       ` Ricard Wanderlof
2011-09-13  9:33   ` Anton Olofsson
2011-09-19  4:53     ` 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=Pine.LNX.4.64.1109120840020.8150@lnxricardw.se.axis.com \
    --to=ricard.wanderlof@axis.com \
    --cc=anol.martinsson@gmail.com \
    --cc=dedekind1@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 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.