From: "Jörg Pfähler" <pfaehler@isse.de>
To: linux-mtd@lists.infradead.org
Subject: UBI: recover_peb and power cut safety
Date: Thu, 16 Jun 2016 10:37:01 +0200 [thread overview]
Message-ID: <1811946.TqycnYvpkR@pfaehler-pc> (raw)
Hi,
I would greatly appreciate some clarification with respect to power cut safety
during writing of an erase block in UBI, specifically power cut safety of
recover_peb.
During a normal write operation (ubi_eba_write_leb in mtd/ubi/eba.c) UBI tries
to move the contents of the block (and the new contents) to a new location via
recover_peb, if the write fails. However, recover_peb does not seem to use the
capability to exchange the (logical) block atomically (as
ubi_eba_atomic_leb_change in mtd/ubi/eba.c does). Specifically, it does not
seem to write the amount of data and its checksum to the VID header. Thus, if
the system crashes in the middle of recover_peb before the old/broken block
could be erased, we are left with a newer version of the block (the sequence
number in the header is increased by recover_peb), but without having moved
all the contents of the old block. This would obviously lead to data loss.
Thus, It seems to me that recover_peb (and therefore ubi_eba_write_leb) is not
power cut safe or is there some other mechanism distinct from the one used by
ubi_eba_atomic_leb_change to achieve this? If not I would suggest using
ubi_eba_atomic_leb_change in ubi_eba_write_leb instead of recover_peb.
Thanks in advance for any clarifications!
Regards,
Jörg
--------------------------------------------------------------------------------------
Jörg Pfähler
Lehrstuhl für Softwaretechnik
Institut für Software and Systems Engineering
Universität Augsburg
Universitätsstr. 6a, Raum 3014
tel: (+49) 821/598-2229
e-mail: joerg.pfaehler@informatik.uni-
augsburg.de<mailto:joerg.pfaehler@informatik.uni-augsburg.de>
--------------------------------------------------------------------------------------
next reply other threads:[~2016-06-16 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 8:37 Jörg Pfähler [this message]
2016-06-16 9:46 ` UBI: recover_peb and power cut safety Richard Weinberger
2016-06-16 10:03 ` Richard Weinberger
2016-06-17 6:37 ` Artem Bityutskiy
2016-06-20 13:48 ` Jörg Pfähler
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=1811946.TqycnYvpkR@pfaehler-pc \
--to=pfaehler@isse.de \
--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