- 09 Jun, 2015 1 commit
-
-
Jeff Sharkey authored
When formatting volumes, pass along fsType string which can be "auto" to let the volume select the best choice. For now, private volumes assume that MMC devices (like SD cards) are best off using f2fs when both kernel support and tools are present, otherwise fall back to ext4. Use blkid when mounting to pick the right set of tools. Move filesystem utility methods into namespaces and place in separate directory to be more organized. Bug: 20275581 Change-Id: Id5f82d8672dda2e9f68c35b075f28232b0b55ed4
-
- 04 Jun, 2015 2 commits
-
-
Paul Lawrence authored
In order to prevent this bug from happening, we must allow vold cryptfs commands to complete while a long running mount is underway. While waiting for vold to be changed to a binder interface, we will simply create two listeners, one for cryptfs and one for everything else. Bug: 19197175 Change-Id: If74142aa81abd58f718a9de6c9e387f6ea442754
-
Paul Lawrence authored
Bug: 21516860 Change-Id: I3153c7f9a414a8eeadc0118f0a642ad8e96c81ce
-
- 29 May, 2015 11 commits
-
-
Elliott Hughes authored
-
Paul Lawrence authored
(cherry-picked from commit 00f4aade5c172534c16070540d1c6c26d0a78c84) Bug: 18151196 Change-Id: Iee0f932c61ff4a309dc2861725b24bf976adb4c7
-
Paul Lawrence authored
(cherry-picked from commit 75c922f49b593f3203ee59c33d00ccb5b3b66ca8) Bug: 18151196 Change-Id: Ideef6bcdbccf068a64ed3e042be50c4837a373f8
-
Paul Lawrence authored
(cherry-picked from commit 29b54aab8ee2d08e2129832364f9b719dd17fa4e) Bug: 18151196 Change-Id: I52ca23b2ce3adcff44bd003d4a12243a0bd6ac34
-
Paul Lawrence authored
(cherry-picked from commit 1190a26f6d7dd34bf10ffc7b367b374d5e591146) As per discussion default permissions are the correct ones. Note that since we use logon keys, they cannot be read outside the kernel. Note also that we limit who can read/write keys in selinux policy. Bug: 18151196 Change-Id: Icc916f430a70eff22e6b74c20ec361c8f3789c1c
-
Paul Lawrence authored
(cherry-picked from commit aaccfac3442ab48f5f94603c07427cc1bb00e12d) Bug: 18151196 Change-Id: I07ffde534dee7d1032149cfcbaa1a61c5246d759
-
Paul Lawrence authored
(cherry-picked from 4e7274551c93e1c064648409f52ca430da647050) Enables OwnerInfo and pattern suppression Bug: 18151196 Change-Id: I46144e16cb00319deeb5492ab82c67f5dd43d6d3
-
Paul Lawrence authored
(cherry-picked from commit 3ca21e227a2e1ed01138a29f450917290a9d1e6e) Handle failures gracefully Change-Id: Ifb6da8c11a86c50fb11964c18cc1be1326461f78
-
Paul Lawrence authored
(cherrypicked from commit 5e7f0042318156ef39c1e4641613f3191ea85b4a) This is one of three changes to enable this functionality: https://android-review.googlesource.com/#/c/146259/ https://android-review.googlesource.com/#/c/146264/ https://android-review.googlesource.com/#/c/146265/ Bug: 18151196 Change-Id: Iba5146b8be1e15050ae901e08b3aaa26d96dcf7e
-
Paul Lawrence authored
(cherry-picked from commit 707fd6c7cccc31c0ab0ec1a6ac8b6077c632fc35) Move all key management into vold Reuse vold's existing key management through the crypto footer to manage the device wide keys. Use ro.crypto.type flag to determine crypto type, which prevents any issues when running in block encrypted mode, as well as speeding up boot in block or no encryption. This is one of four changes to enable this functionality: https://android-review.googlesource.com/#/c/148586/ https://android-review.googlesource.com/#/c/148604/ https://android-review.googlesource.com/#/c/148606/ https://android-review.googlesource.com/#/c/148607/ Bug: 18151196 Change-Id: I3c68691717a61b5e1df76423ca0c02baff0dab98
-
Elliott Hughes authored
Bug: http://b/20501816 Change-Id: Ia0a3899947582b8dd0e8e185c203d1ad7dad572e
-
- 19 May, 2015 2 commits
-
-
Jeff Sharkey authored
Useful for transforming a secondary SD card slot into a primary SD card slot without doing a completely different lunch target. $ adb shell stop $ adb shell setprop vold.debug.default_primary 1 $ adb shell setprop ro.vold.primary_physical 1 $ adb shell setprop ctl.restart vold $ adb shell start Bug: 21017105 Change-Id: I45aac7ab3bb4c5ac3e0140572844883823fc3e4f
-
Jeff Sharkey authored
Also drop unneeded SCR register logging. Bug: 21172095 Change-Id: I17c5aae2edc0eb7144ab38701f90a1fd54e119da
-
- 16 May, 2015 2 commits
-
-
Elliott Hughes authored
-
Elliott Hughes authored
Bug: http://b/20501816 Change-Id: Ieecce9304539c250ed1728252b8c2c09d29afd7f
-
- 15 May, 2015 1 commit
-
-
Jeff Sharkey authored
Now that we're offering to store private app data on adopted storage devices, the performance of those devices is much more important to overall user experience. To help set user expectations, this change offers to execute a real-world benchmark on a storage device, returning a metric that can be used to compare internal and external storage. The benchmark is generated from the strace-instrumented storage access patterns of typical apps. A typical device completes the benchmark in under two seconds on internal storage, a UHS-3 SD card is even faster (!), but a very slow Class 4 SD card takes about 30 seconds to complete, giving us a clear signal. The measured benchmark numbers are logged along with information about the storage device, such as manufacturer, model, etc. Card serial numbers are scrubbed from output. Bug: 21172095 Change-Id: I9b2713dafdfdfcf5d97bf1bc21841f39409a7e54
-
- 13 May, 2015 2 commits
-
-
Jeff Sharkey authored
Bug: 19993667 Change-Id: I3c3dddab157a11038f7160d24d53e728bde2194f
-
Jeff Sharkey authored
Used by framework to bypass FUSE daemon overhead in some cases. Bug: 21017105 Change-Id: I2f3ae70607417fc4cd2c970cb17cf3afa2f42613
-
- 30 Apr, 2015 2 commits
-
-
Jeff Sharkey authored
-
Jeff Sharkey authored
Since otherwise we might have a stale path. Bug: 19993667 Change-Id: I099e3dc0c5aa9ab6820cded4f2ae7fd6bf18ea40
-
- 29 Apr, 2015 3 commits
-
-
Jeff Sharkey authored
Change-Id: Ia11c689c373f41b2a63bc84151eb16f7c7b9d155
-
Jeff Sharkey authored
Bug: 19993667 Change-Id: Ie226e06edcb426caca2dbc97d2d5d60ae948c85e
-
Jeff Sharkey authored
Bug: 19993667 Change-Id: If6a79391e34b652b2ba4e6df40a8e712f7a2e172
-
- 25 Apr, 2015 4 commits
-
-
Elliott Hughes authored
* commit '85c7c08e': Wait for completion of device mapping in mountObb
-
Elliott Hughes authored
* commit 'd5aa67cc': Wait for completion of device mapping in mountObb
-
Elliott Hughes authored
-
yoshiyuki hama authored
The VolumeManager::mountObb() creates a mapping between a loopback device and a dm device. However the device-mapper carries it out asynchronously, so there is a possibility that Vold accesses to the dm device which is being built. Added waiting for completion of the mapping in that function, like mountAsec(). To verify install FrameworksCoreTests.apk and do: adb shell am instrument -r -w -e class android.os.storage.\ StorageManagerIntegrationTest#testMountTwoEncryptedObb \ com.android.frameworks.coretests/android.test.\ InstrumentationTestRunner Change-Id: If42f4b7494bb2f8a8b72d106ad84b3e3bf91fd9b
-
- 24 Apr, 2015 1 commit
-
-
Jeff Sharkey authored
When requested, kick off a thread that will migrate storage contents between two locations. This is performed in several steps that also interact with the framework: 1. Take old and new volumes offline during migration 2. Wipe new location clean (10% of progress) 3. Copy files from old to new (60% of progress) 4. Inform framework that move was successful so it can persist 5. Wipe old location clean (15% of progress) Derives a hacky progress estimate by using a rough proxy of free disk space changes while a cp/rm is taking place. Add new internal path for direct access to volumes to bypass any FUSE emulation overhead, and send it to framework. Remove mutex around various exec calls since setexeccon() is already per-thread. Bug: 19993667 Change-Id: Ibcb4f6fe0126d05b2365f316f53e71dc3e79a2b8
-
- 21 Apr, 2015 1 commit
-
-
Jeff Sharkey authored
We eventually should move back to per-disk locks, but use a giant lock to keep development rolling forward. Also move force adoptable flag to framework since, since encrypted devices don't have persisted properties loaded early during boot. Bug: 19993667 Change-Id: Ifa3016ef41b038f8f71fc30bc81596cfd21dcd2a
-
- 19 Apr, 2015 2 commits
-
-
Jeff Sharkey authored
Bug: 19993667 Change-Id: I47099c262686127f82dd376570d49cf0ad119842
-
Jeff Sharkey authored
Bug: 19993667 Change-Id: I20dc183a35c11b5b4ba6139e690929b9c279b830
-
- 18 Apr, 2015 2 commits
-
-
Jeff Sharkey authored
Use system log for more durable log history. Also accept persistable version of flag to force adoptability. Bug: 19993667 Change-Id: Icdf36799e26038e9a8e2bdaca276d97b22ba3941
-
Jeff Sharkey authored
This is cleaner and more direct than the reverse of having the disk publish child volume membership. Rename state constants to match public API. Add state representing bad removal. Make it clear that volume flags are related to mounting. Send new unsupported disk event when we finish scanning an entire disk and have no meaningful volumes. Bug: 19993667 Change-Id: I08a91452ff561171a484d1da5745293ec893aec0
-
- 15 Apr, 2015 2 commits
-
-
Jeff Sharkey authored
Otherwise we get really excited and trip over ourselves while partitions are still being created. Bug: 19993667 Change-Id: I034e56b3063a71d73f9311a945c05ea2ae255f7d
-
Jeff Sharkey authored
Bug: 19993667 Change-Id: Id125d9252bf7130516c0ec619d5f067fea24d560
-
- 14 Apr, 2015 1 commit
-
-
Jeff Sharkey authored
Bug: 19993667 Change-Id: Ib15e79a94a185843dace35fea7daaea866120f87
-
- 13 Apr, 2015 1 commit
-
-
Jeff Sharkey authored
Bug: 19993667 Change-Id: I17093f0f9abe8762e5ee4f38ce99f9024e419dfc
-