Gabe Black be48f3e41e cbfstool: Propogate compression errors back to the caller. ... When compression fails for whatever reason, the caller should know about it rather than blindly assuming it worked correctly. That can prevent half compressed data from ending up in the image. This is currently happening for a segment of depthcharge which is triggering a failure in LZMA. The size of the "compressed" data is never set and is recorded as zero, and that segment effectively isn't loaded during boot. BUG=chrome-os-partner:26060 TEST=Built with this change and saw that cbfstool no longer seems to succeed or inserts a broken payload. BRANCH=None Change-Id: Idbff01f5413d030bbf5382712780bbd0b9e83bc7 Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: https://chromium-review.googlesource.com/187364 Reviewed-by: Hung-Te Lin <hungte@chromium.org> Tested-by: Gabe Black <gabeblack@chromium.org> Commit-Queue: Gabe Black <gabeblack@chromium.org>		2014-02-24 13:35:19 +00:00
..
C	cbfstool: remove dead code	2013-11-14 02:38:23 +00:00
lzma.c	cbfstool: Propogate compression errors back to the caller.	2014-02-24 13:35:19 +00:00