Different blkid and fsck execution domains.
vold works with two broad classes of block devices: untrusted devices
that come in from the wild, and trusted devices like PrivateVolume
which are encrypted.
When running blkid and fsck, we pick which SELinux execution domain
to use based on which class the device belongs to.
Bug: 19993667
Change-Id: I2695f028710a4863f0c3b2ed6da437f466401272
diff --git a/PublicVolume.cpp b/PublicVolume.cpp
index f3bd905..ffcfc67 100644
--- a/PublicVolume.cpp
+++ b/PublicVolume.cpp
@@ -51,7 +51,7 @@
}
status_t PublicVolume::readMetadata() {
- status_t res = ReadMetadata(mDevPath, mFsType, mFsUuid, mFsLabel);
+ status_t res = ReadMetadataUntrusted(mDevPath, mFsType, mFsUuid, mFsLabel);
VolumeManager::Instance()->getBroadcaster()->sendBroadcast(
ResponseCode::VolumeFsTypeChanged,