summaryrefslogtreecommitdiff
path: root/update_boot_flags_action.h
diff options
context:
space:
mode:
authorxunchang <xunchang@google.com>2019-04-25 10:37:36 -0700
committerTianjie Xu <xunchang@google.com>2019-04-26 13:44:50 -0700
commitf6fd73661bebb7fec2a672da29379a7fe4e6c0eb (patch)
tree904b1a546cbcd8393a95dacfe394eb5adfcab087 /update_boot_flags_action.h
parent23ba59e60ffe386e1f7a35883355aefa6fa9089d (diff)
Set the block device to be writable before writing verity data
The block device is set to be writable when the delta performer opens the partition to perfrom writes. But if the update interrupts and the device reboots during the verity data calculation, update engine will consider the write actions done on resumes and skip setting the writable flag. As a result, the resumed update will fail to write the hashtree with EPERM. A possible fix is to explicltly set the flag when the FilesystemVerifierAction wants to write verity data. Bug: 131232680 Test: Interrupt the update during verity writing, reboot and check the update resumes correctly Change-Id: I1007414139e4ae5be3fc60ec73b18264d4baa60e
Diffstat (limited to 'update_boot_flags_action.h')
0 files changed, 0 insertions, 0 deletions