From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI: ignore/overwrite old data/PEBs after flashing
Date: Mon, 20 Oct 2014 16:47:25 +0300 [thread overview]
Message-ID: <1413812845.7906.291.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CACna6rwe46Umvt9SFYTsfEjUPU7yY7oyJXbdovYehQrNfLwNQA@mail.gmail.com>
On Thu, 2014-10-16 at 15:51 +0200, Rafał Miłecki wrote:
> Unfortunately this won't work if we flash the same firmware twice (it
> will contain the same sequence). Imagine someone flashing a stable
> OpenWrt release, then breaking something and flashing the same image
> again. It'll contain the same sequence number and my magic driver
> won't clean the old data :(
Yes, flashing with ubiformat would be fine, because it changes the
sequence number on-the-fly. With industial flashers, you'd need to erase
the flash.
Now you say you do not have the erase operation. You idea of a
"IMAGE_ENDS_HERE" bit seems to be nice, and you could implement it, but
you should think about the fastmap case too. Probably you need to do
nothing, because fastmap will only refer the PEBs within the image, and
the PEBs outside of the image will be scheduled for erasure. But you
should verify this.
Artem.
next prev parent reply other threads:[~2014-10-20 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 5:34 UBI: ignore/overwrite old data/PEBs after flashing Rafał Miłecki
2014-10-16 9:10 ` Richard Weinberger
2014-10-16 10:21 ` Rafał Miłecki
2014-10-16 11:30 ` Artem Bityutskiy
2014-10-16 10:09 ` Artem Bityutskiy
2014-10-16 10:29 ` Rafał Miłecki
2014-10-16 10:40 ` Artem Bityutskiy
2014-10-16 11:17 ` Rafał Miłecki
2014-10-16 11:27 ` Artem Bityutskiy
2014-10-16 11:38 ` Rafał Miłecki
2014-10-16 11:54 ` Artem Bityutskiy
2014-10-16 13:51 ` Rafał Miłecki
2014-10-20 13:47 ` Artem Bityutskiy [this message]
2014-10-20 18:40 ` Rafał Miłecki
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=1413812845.7906.291.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nbd@openwrt.org \
--cc=zajec5@gmail.com \
/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