Policy implementation for encryptfs to ext4 migration strategy

chrome/browser/chromeos/login/startup_utils.h

Index: chrome/browser/chromeos/login/startup_utils.h
diff --git a/chrome/browser/chromeos/login/startup_utils.h b/chrome/browser/chromeos/login/startup_utils.h
index 6f9d4ef18dd36ec60b3602e875b1b988d96b3422..ad2fa3c608c0f575c888200bc62f3e183d8680e1 100644
--- a/chrome/browser/chromeos/login/startup_utils.h
+++ b/chrome/browser/chromeos/login/startup_utils.h
@@ -70,6 +70,13 @@ class StartupUtils {
 
   // Registers OOBE preferences.
   static void RegisterPrefs(PrefRegistrySimple* registry);
+
+  // Sets the flag in arc_utils to set if device is allowed to migrate the user
+  // data from ecryptfs to ext4 encryption. This is true when the device is not
+  // managed or when the DeviceEcryptfsMigrationStrategyProto device policy
+  // allows migration. Ext4 is required for ARC(N+).
+  // TODO(igorcov): Remove this after migration. crbug.com/725493
+  static void SetExt4MigrationForArcAllowed();

[hidehiko, 2017/05/25 12:41:55]

Which thread this can be called? Only UI thread? Please comment.

 };
 
 }  // namespace chromeos