Google Git
Sign in
android / platform / system / libvintf / 856b7bd42c5dc8922d79a64af432ecc929bd740c
commit856b7bd42c5dc8922d79a64af432ecc929bd740c[log] [tgz]
authorYifan Hong <elsk@google.com>Mon Nov 05 14:00:30 2018 -0800
committerYifan Hong <elsk@google.com>Wed Nov 07 12:59:17 2018 -0800
tree3dd194a3c389799c4f4f8986067ba32a63d47ce2
parentaf3713ec4ce6b65ef084c1c0c1fb64085d5fd332 [diff]
VintfObjectRecovery: mount all partitions in fstab

Specifically, ODM partition should be mounted when ODM manifest is loaded.

Previously, the on-device vendor manifest is not loaded correctly
because the ODM partition is never mounted. This can potentially
break framework-only OTAs.

For this to work, it requires a mount path for /odm to be in fstab.

If we are going to load VINTF metadata from partitions other than
/system, /vendor, /odm, the current code still works as long as the
mount path for /foo exists in fstab.

Test: manual OTA
Bug: 118635062
Change-Id: I9d02e36f262d4d0ca31f8b43dfe4486f13a2faa1
1 file changed
tree: 3dd194a3c389799c4f4f8986067ba32a63d47ce2
  1. analyze_matrix/
  2. include/
  3. include-test/
  4. test/
  5. .clang-format
  6. Android.bp
  7. Android.mk
  8. assemble_vintf_main.cpp
  9. AssembleVintf.cpp
  10. check_vintf.cpp
  11. CompatibilityMatrix.cpp
  12. FileSystem.cpp
  13. HalInterface.cpp
  14. HalManifest.cpp
  15. KernelConfigParser.cpp
  16. KernelConfigTypedValue.cpp
  17. main.cpp
  18. ManifestHal.cpp
  19. ManifestInstance.cpp
  20. MatrixHal.cpp
  21. MatrixInstance.cpp
  22. MatrixKernel.cpp
  23. MODULE_LICENSE_APACHE2
  24. NOTICE
  25. OWNERS
  26. parse_string.cpp
  27. parse_xml.cpp
  28. PREUPLOAD.cfg
  29. PropertyFetcher.cpp
  30. Regex.cpp
  31. RuntimeInfo-host.cpp
  32. RuntimeInfo-target.cpp
  33. RuntimeInfo.cpp
  34. SystemSdk.cpp
  35. TransportArch.cpp
  36. utils.h
  37. VintfObject.cpp
  38. VintfObjectRecovery.cpp
  39. XmlFile.cpp