tree d0771fbbb456fca95239ccb96ffa00aaea6eaf58
parent 4f39da8e8db32fb8e0aed5ec8734b6be22e0eadb
author Kelvin Zhang <zhangkelvin@google.com> 1655918334 -0700
committer Akilesh Kailash <akailash@google.com> 1656376276 +0000

Fix partition mapping bug


After installing a VABC OTA and device reboots, merge happens. Some OTA states are cached in memory during the merge process. When the 2nd OTA comes, update_engine will incorrectly think the 2nd OTA is also a VABC update, resulting in incorrectly mapped partitions. Then update_engine will extract data from OTA and write them to source partitions, causing verity error and bricking the device. This CL fixes the corruption bug by create a new instance of SnapshotManager for each new OTA. This prevents
us from reading stale data cached in SnapshotManager member variables.


Bug: 229708688
Bug: 236348265
Test: Apply VABC OTA, reboot, then apply VAB OTA
Change-Id: If4d1de8393ce0329b825c06e567b985e9d89680b
(cherry picked from commit c675fc0aaa6f9e4d88d040847435f2487ff9a2d3)
Merged-In: If4d1de8393ce0329b825c06e567b985e9d89680b