- 06 Sep, 2016 1 commit
-
-
Wei Wang authored
This is part of the change to support early/late fstab mounting in order to support starting key services before /data mounting fs_mgr_mount_all function updated with a parameter to support mounting mode More information refer to init/readme.txt (cherry picked from commit 1d6476c3c848ebc8fbdfa6945e1c3be447beb5a3) Bug: 30118894 Change-Id: I5e925b900fd477f230a90514cc2b561c7a7e9f49
-
- 31 Aug, 2016 1 commit
-
-
Jeff Sharkey authored
For adoptable storage and FBE to coexist we need a new dm-biocrypt kernel feature which isn't ready yet. So for now, prevent devices from being adopted on FBE devices. Bug: 30770036 Change-Id: I47639209161ee403ce13ea9a60da235e97c3fc30 (cherry picked from commit 157175110948b3cf604e40420059aa5265039847)
-
- 25 Jul, 2016 1 commit
-
-
Paul Crowley authored
Ephemeral users don't have keys stored on disk at all, so it's neither necessary nor possible to manipulate the disk keys here. Bug: 30038313 Change-Id: Idc7ec1bfe1e8a6ffa6cee2f284dbe378097b08da
-
- 21 Jul, 2016 1 commit
-
-
Paul Crowley authored
This can happen when cleaning up stale users at boot time. Bug: 30158800 Change-Id: I2733d8d525fc79b7f05eb2225b7e6e14c4da277f
-
- 19 Jul, 2016 1 commit
-
-
Paul Crowley authored
Work around a kernel bug that was causing lockups. Bug: 30225438 Change-Id: Ia6eb60774037e692351af8eaed98b79596ea3635
-
- 18 Jul, 2016 1 commit
-
-
Jeff Sharkey authored
On FBE devices, the filenames inside credential-encrypted directories are mangled until the key is installed. This means the initial restorecon at boot needs to skip these directories until the keys are installed. This CL uses an existing facility to request that init run a recursive restorecon over a given path, and it requests that operation for the CE directories that would have been omitted by the SKIPCE flag earlier during boot. Bug: 30126557 Change-Id: I8c7abea27215075a091f615a7185a82a2f4a4a95
-
- 13 Jul, 2016 2 commits
-
-
Paul Crowley authored
-
Paul Crowley authored
-
- 12 Jul, 2016 2 commits
-
-
Paul Crowley authored
Don't rely on cryptographic binding of secdiscard to key; securely delete the other information needed to reconstruct the key too. Bug: 26021231 Change-Id: If03d2c051b0ec2fdcb5c6f70bde7e3287424f216
-
Paul Crowley authored
On a device where we can't BLKSECDISCARD sectors, we "overwrite" them with zeroes. This changes the FTL to remap those sectors to new locations. With this done, the old contents are accessible only given a compromise of flash firmware or a die level attack. Bug: 26021231 Change-Id: Ia065921389886fac1ba456c19c138187237c2561
-
- 06 Jul, 2016 3 commits
-
-
Henrik Baard authored
When "migrating" data failes due to insufficient space at target location, the data copied so far is left in target location, which in practice is now filled to the brim. If copy fails clean up the data copied so far since user has the data in original location. Bug: 26322200 Change-Id: Iab29a7f9e653e6857ee0e2723d151dfec81b14dd
-
Henrik Baard authored
Sometimes migrating data fails to mount the target volume after operation is finished. MoveTask is running in its own thread, copying data between external card and internal memory. After copying the data the method "bringOnline" is run. This method destroys and creates the volumes. When VolumeBase::create() is run it will notify MountService, who upon receiving this notification will send a mount command to mount the new primary storage. This command will sometimes run before setState(State::kUnmounted); is called on the newly created volume. This will cause the mount command to fail. VoldConnector: SND -> {10 volume mount emulated 3 -1} vold : emulated flags change requires state unmounted or unmountable vold : emulated user change requires state unmounted or unmountable vold : emulated mount requires state unmounted or unmountable Lock bringOnline so no volume commands will be processed until volumes are (re-)created and have correct state. Bug: 26322200 Change-Id: I4aba85c226d904c42ae9edcdfec21619218939d6
-
Jeff Sharkey authored
This had minimal impact on the results, since 95% of the writes were performed through pwrite(), but it's important to fix this for future benchmark suites. Bug: 29759783 Change-Id: Ic628aab98b9f9def78508cc722899afdefed84ae
-
- 29 Jun, 2016 1 commit
-
-
Yabin Cui authored
Bug: 29582118 Change-Id: I8de2cfbc62908011dba2ab86d17f977ebcfadac0
-
- 22 Jun, 2016 1 commit
-
-
Paul Lawrence authored
Only merge once https://partner-android-review.googlesource.com/#/c/619829/1 has been merged into kernel. Bug: 28779973 Change-Id: Icef78d1e4381e89e07797c36f6f650033d313557
-
- 27 May, 2016 1 commit
-
-
Paul Lawrence authored
Bug: 28905864 Change-Id: Ie2a5c3e029075d53a86ef3afb7fe364c16d8d52b
-
- 23 May, 2016 1 commit
-
-
Paul Lawrence authored
This reverts commit 01f1bc72. Bug: 28905864 Change-Id: I489f5d073530438829038630af7af6b2a5cbdbbe
-
- 18 May, 2016 1 commit
-
-
Paul Crowley authored
am: a363036b * commit 'a363036b': Two phases to set the password for disk encryption Change-Id: Ia28823079d8c0bda220238339f28095b234a0ae5
-
- 17 May, 2016 1 commit
-
-
Paul Crowley authored
Revert "Revert "Two phases to set the password for disk encryption"" This reverts commit d4023892. In addition, fix the bug in the original commit. Bug: 28154455 Bug: 28694324 Change-Id: I885f1d73e739416347c135d79979941c2bbdbe62
-
- 11 May, 2016 1 commit
-
-
Paul Lawrence authored
Bug: 28616054 Change-Id: If3fddd62f069c7e3e8369a1db68e69c390059d63
-
- 10 May, 2016 5 commits
-
-
Paul Crowley authored
am: cfa03d4a * commit 'cfa03d4a': e4crypt_is_native has been moved into system/extras. Change-Id: I345475c44fb2d8812a25c9f2195c748cddc55bfe
-
Paul Crowley authored
-
Paul Crowley authored
am: d4023892 * commit 'd4023892': Revert "Two phases to set the password for disk encryption" Change-Id: I53a3804fc7bff9c99840aeee36fc4b7ff8e46ac1
-
Paul Crowley authored
This reverts commit 92c5eeb4. Bug: 28694324 Change-Id: Ibbbaff287f4dd28f4a13e122a3617987a8875a44
-
Paul Crowley authored
Bug: 28318405 Change-Id: Id962764cf7fb5f58b769bf99aeb6d3d69cb66991
-
- 09 May, 2016 1 commit
-
-
Paul Crowley authored
am: 92c5eeb4 * commit '92c5eeb4': Two phases to set the password for disk encryption Change-Id: I82c1cfa2874ac4709e42f5c2047c832cbcaccb91
-
- 06 May, 2016 1 commit
-
-
Paul Crowley authored
In one phase, we make the new password work, and in the second we make it the only one which works ("fixation"). This means that we can set the password in Gatekeeper between these two phases, and a crash doesn't break things. Unlocking a user automatically fixates the presented credential. Bug: 28154455 Change-Id: I54623c8652f0c9f72dd60388a7dc0ab2d48e81c7
-
- 29 Apr, 2016 2 commits
-
-
Paul Lawrence authored
-
Paul Lawrence authored
Note that this is an ugly workaround for a kernel bug. Bug: 28373400 Change-Id: Iec1ae53f4e18f06e41e8cf1fcc3ab03fc9848632
-
- 27 Apr, 2016 2 commits
-
-
Paul Crowley authored
am: b3de337a * commit 'b3de337a': Use a longer timeout on the disk encryption keys Change-Id: Ieadec9da13383361ac76bf6b79ecea948965a1d9
-
Paul Crowley authored
Avoid a timeout error by extending the time allowed between getting the auth token and decrypting the key from five to thirty seconds. Bug: 28398766 Change-Id: I1dbb9e0e33707e7de4c1720ad1b8e153c77094b2
-
- 25 Apr, 2016 4 commits
-
-
John Cormie authored
am: a4330beb * commit 'a4330beb': Unmount public sdcard filesystems before killing the fuse process. Change-Id: I294d46bb27fb6d8ac83f1041e849fd366134b6ee
-
John Cormie authored
-
Martijn Coenen authored
am: 47ff14ad * commit '47ff14ad': Move vold (and sdcard childs) to foreground cpuset. Change-Id: I2d539472902f0f2ce33bbfe767f93b9bf91856ce
-
Martijn Coenen authored
-
- 19 Apr, 2016 3 commits
-
-
John Cormie authored
Avoids ENOTCONN during eject for sdcard users. Change-Id: I7b89ccaad4bb7af3639dc0b702168030a2f88366 Bug: 28268676
-
Paul Lawrence authored
am: 0264d8ff * commit '0264d8ff': Don't start defaultcrypto twice Change-Id: I39951628d41f656901658cd82a56298ef9f663ec
-
Paul Lawrence authored
-
- 18 Apr, 2016 2 commits
-
-
Paul Lawrence authored
The old way (using triggers) starts defaultcrypto twice because queue_property_triggers_action retriggers the action. Bug: 27452459 Change-Id: I715d5441f8ae0b820b680f6a75f51694c4420992
-
Jeff Sharkey authored
am: be70c9ae * commit 'be70c9ae': Consistent creation/destruction of user data. Change-Id: I55f4fe88a8c02d019fa92028e6ad358fc0f75aeb
-