summaryrefslogtreecommitdiff
path: root/apexer/apexer.py
diff options
context:
space:
mode:
authorJooyung Han <jooyung@google.com>2019-04-11 15:12:09 +0900
committerJooyung Han <jooyung@google.com>2019-06-18 23:35:21 +0900
commitf7c8d039bfc2b59d5ec3377776c1ba907e5ed076 (patch)
treeaae8bb9dbd2453d71c3d988328bcd3572a65ac79 /apexer/apexer.py
parent11fa689b34d9599996b79317fac628ce972d52de (diff)
apexd: support zero-hash on dm-verity mount
When activating APEX package which has zero-ed hashtree for smaller OTA update size, APEXD generates hashtree on device and stores it for later use in /data/apex/hashtree/. Note that dm-verity allows us to create a device with separate hash device and it should be a block device. So, we need an additional loop device for hash. TODOs: - remove unused hashtree files on boot complete - set unique name for hashtree file instead of package id(name@ver). package id may not be unique among APEX files. - database entries for additional loop device(hashtree) - tests Bug: 120058143 Test: activate via dm-verity with generated hashtree Change-Id: Id75dec08897f96628f3b45eeadcb552e9ffc87ab
Diffstat (limited to 'apexer/apexer.py')
0 files changed, 0 insertions, 0 deletions