Call fs_mgr_overlayfs_is_setup() in InitPartitionMetadata
am: 62b42c896e
Change-Id: I4d584fdcc6206a04f7f05f40da9e98f3d1c581a8
diff --git a/boot_control_android.cc b/boot_control_android.cc
index c42c8d7..af1a5f9 100644
--- a/boot_control_android.cc
+++ b/boot_control_android.cc
@@ -26,6 +26,7 @@
#include <bootloader_message/bootloader_message.h>
#include <brillo/message_loops/message_loop.h>
#include <fs_mgr.h>
+#include <fs_mgr_overlayfs.h>
#include "update_engine/common/utils.h"
#include "update_engine/dynamic_partition_control_android.h"
@@ -396,6 +397,13 @@
bool BootControlAndroid::InitPartitionMetadata(
Slot target_slot, const PartitionMetadata& partition_metadata) {
+ if (fs_mgr_overlayfs_is_setup()) {
+ // Non DAP devices can use overlayfs as well.
+ LOG(WARNING)
+ << "overlayfs overrides are active and can interfere with our "
+ "resources.\n"
+ << "run adb enable-verity to deactivate if required and try again.";
+ }
if (!dynamic_control_->IsDynamicPartitionsEnabled()) {
return true;
}