Use snapshot value sys.fuse_snapshot instead of persist.sys.fuse
This will allow us to receive values from server flags and store them in
persist.sys.fuse without risking flag consistency during a boot.
Test: manual - flip persist.sys.fuse both ways and make sure FuseDaemon
works as expected.
Bug: 140803239
Change-Id: I839a1973c98b4eda982226d20be48d1c08e7464a
diff --git a/VolumeManager.cpp b/VolumeManager.cpp
index adb4a5c..5b23116 100644
--- a/VolumeManager.cpp
+++ b/VolumeManager.cpp
@@ -382,7 +382,7 @@
}
int VolumeManager::linkPrimary(userid_t userId) {
- bool isFuse = GetBoolProperty(android::vold::kPropFuse, false);
+ bool isFuse = GetBoolProperty(android::vold::kPropFuseSnapshot, false);
if (isFuse) {
// Here we have to touch /mnt/user/userid>/<volumeid> which was already mounted as part of
@@ -464,7 +464,7 @@
}
int VolumeManager::remountUid(uid_t uid, int32_t mountMode) {
- if (GetBoolProperty(android::vold::kPropFuse, false)) {
+ if (GetBoolProperty(android::vold::kPropFuseSnapshot, false)) {
// TODO(135341433): Implement fuse specific logic.
return 0;
}