diff options
author | Artem Bityutskiy <artem.bityutskiy@intel.com> | 2011-09-11 13:52:08 +0300 |
---|---|---|
committer | Artem Bityutskiy <artem.bityutskiy@intel.com> | 2011-09-19 07:52:49 +0300 |
commit | d9cbf6a5b3e6d535eed2e9b28257562ba9e2a515 (patch) | |
tree | 00a7e34e73f4abbceb8f78e1befc6dcd562ce327 /tests/fs-tests/stress/atoms/pdfrun.c | |
parent | bf01f2960ba82468b1b25f00e044fd0c3ee0770a (diff) |
ubiformat: handle write errors correctly
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.
This patch fixes this issue - in case of a write error, we preserve the current
data and write it to the next eraseblock, instead of dropping it.
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@intel.com>
Diffstat (limited to 'tests/fs-tests/stress/atoms/pdfrun.c')
0 files changed, 0 insertions, 0 deletions