commit | 71e182bc3879a53f04a50de9d25c333163cb7c76 | [log] [tgz] |
---|---|---|
author | Tianjie Xu <xunchang@google.com> | Wed Aug 31 18:06:33 2016 -0700 |
committer | Tianjie Xu <xunchang@google.com> | Wed Aug 31 19:11:41 2016 -0700 |
tree | 4f116fad73bb81476238deb9a70313f54cd68246 | |
parent | 818394869d36b9db1bf4984585a062d4bb91310f [diff] |
Check an edge case when read(2) returns 0 We might end up in an infinite loop if read(2) reached EOF unexpectedly. The problematic code in uncrypt mentioned in the bug has been fixed by switching to libbase ReadFully(). So I grepped through the recovery code and fixed some other occurences of the issue. Bug: 31073201 Change-Id: Ib867029158ba23363b8f85d61c25058a635c5a6b
mm -j && m ramdisk-nodeps && m recoveryimage-nodeps # To boot into the new recovery image # without flashing the recovery partition: adb reboot bootloader fastboot boot $ANDROID_PRODUCT_OUT/recovery.img
# After setting up environment and lunch. mmma -j bootable/recovery # Running the tests on device. adb root adb sync data # 32-bit device adb shell /data/nativetest/recovery_unit_test/recovery_unit_test adb shell /data/nativetest/recovery_component_test/recovery_component_test # Or 64-bit device adb shell /data/nativetest64/recovery_unit_test/recovery_unit_test adb shell /data/nativetest64/recovery_component_test/recovery_component_test