- 06 Nov, 2014 3 commits
-
-
Dan Albert authored
* commit '36859212': Move vold to libc++.
-
Dan Albert authored
* commit '460a93a6': Move vold to clang so ASAN_ALL works.
-
Dan Albert authored
-
- 05 Nov, 2014 1 commit
-
-
Dan Albert authored
Bug: 15193147 Change-Id: Ib868f1ed8145ca5cbfdb4cd60ed0c47a6182ac62
-
- 21 Oct, 2014 2 commits
-
-
Dan Albert authored
-
Dan Albert authored
ASAN_ALL uses ASAN for anything built with clang. Since some of vold's dependencies use clang, they will have unresolved ASAN symbols unless vold is also built with clang. There's no harm in just moving this project to clang. Change-Id: Ia6f412beb7bf092121bff2a5a980531636adcdb9
-
- 18 Oct, 2014 2 commits
-
-
Nick Kralevich authored
* commit 'ab083da0': Set SELinux contexts on device nodes created by vold.
-
Nick Kralevich authored
-
- 17 Oct, 2014 1 commit
-
-
JP Abgrall authored
automerge: 512f0d52 * commit '512f0d52': cryptfs: [HACK] reboot if the crypto block dev failed to open
-
- 16 Oct, 2014 2 commits
-
-
JP Abgrall authored
* commit '7776871d': cryptfs: extra debugging around crypto blockdev dm-... errors.
-
JP Abgrall authored
There are cases where the /dev/block/dm-0 fails to open. This leads to the device not completing the boot up sequence. Currently, the only way out is to reboot. Bug: 17898962 Change-Id: If4583ebb1ef1ebdbaf680d69b876459aaec2f4ce (cherry picked from commit 7fc1de8a)
-
- 10 Oct, 2014 1 commit
-
-
JP Abgrall authored
Some times the /dev/block/dm-0 fails to open after it has been setup. Log why. Bug: 17576594 Bug: 17942270 Change-Id: If0bbfe22d84137f2029bacb10873832038f0d36c
-
- 06 Oct, 2014 2 commits
-
-
Paul Lawrence authored
* commit 'fc615041': Remove possibility of zero chars from passwords
-
Paul Lawrence authored
scrypt pads the password with zeros. Our patterns use 0 to represent the top left dot. So patterns that end there are equivalent to ones that end one short. After much thought, the best solution is to change the way we represent patterns in keyguard. This, however, is a big change. The short term solution is to change the pattern representation in vold so that we are storing the correct thing. Later we will change keyguard to handle patterns correctly and remove quite a few hacks from vold (use of hex, this code). b/17840293 created to track this. Bug: 17751714 Change-Id: I30cdffb0f0db406d2e2b6c54d4153d120d975318
-
- 05 Oct, 2014 3 commits
-
-
Paul Lawrence authored
* commit '7639a6ab': Reset failed decryption count on successful decryptions
-
Paul Lawrence authored
-
Paul Lawrence authored
Bug: 17866359 Change-Id: I1af2ff1ac4f5243afba0cfa2f2d3a1d0b029091b
-
- 03 Oct, 2014 2 commits
-
-
Greg Hackmann authored
* commit '6e8440fd': cryptfs: kill processes with open files on tmpfs /data
-
Greg Hackmann authored
cryptfs will fail to remount /data at boot if any processes (e.g. dex2oat) have files open on the tmpfs /data partition. Since these files are about to be destroyed anyway, just kill the offending processes: first with SIGHUP and finally with SIGKILL. Also remove a stray i++ that effectively cut the number of retries in half. Bug: 17576594 Change-Id: I76fb90ce2e52846ffb9de706e52b7bde98b4186a Signed-off-by:
Greg Hackmann <ghackmann@google.com>
-
- 30 Sep, 2014 3 commits
-
-
Stephen Smalley authored
Extend vold to look up and set SELinux contexts on the device nodes it creates for extra loop devices and for volumes. Prior to this change, these device nodes simply inherited the type of their parent directory /dev/block, i.e. block_device, and vold therefore required create_file perms to block_device:blk_file. With this change we can scope vold down to accessing specific block device types. This depends on change Id3bea28f5958086716cd3db055bea309b3b5fa5a to allow vold to use setfscreatecon(). Change-Id: Ib9e8294abb1da94d92503947603ec12e802ff08c Signed-off-by:
Stephen Smalley <sds@tycho.nsa.gov>
-
Paul Lawrence authored
* commit '9c58a871': Use monotonic clock for cryptfs progress
-
Paul Lawrence authored
Otherwise we get strange results when the time changes. Worst effect is that the encryption takes a lot longer since we are calling the logging code far more frequently. Bug: 17625981 Change-Id: Ice29f28b3720e9e4a1ea28e45eeab574d1959ec1
-
- 24 Sep, 2014 8 commits
-
-
Greg Hackmann authored
* commit '3574b085': cryptfs: log umount() failure reason
-
Greg Hackmann authored
* commit '46a3a79a': print information about opened files when failed unmount
-
Jeff Sharkey authored
* commit 'dd1a8040': Include reason when wiping data.
-
Greg Hackmann authored
-
Greg Hackmann authored
-
Greg Hackmann authored
Bug: 17576594 Change-Id: I7320aa597210896b4db6e663e1b2cb0c24d96557 Signed-off-by:
Greg Hackmann <ghackmann@google.com>
-
jessica_yu authored
Change-Id: I88ae719cdae490433390d624f75612a9f4f96677 Cryptfs : Enabling support for allow_discards in dmcrypt. Cryptfs : Password matches Cryptfs : test_mount_encrypted_fs(): Master key saved TrustyKeymaster: Creating device TrustyKeymaster: Device address: 0x7f8f416100 Cryptfs : keymaster version is 3 Cryptfs : Just asked init to shut down class main ServiceManager: service 'drm.drmManager' died ServiceManager: service 'media.audio_flinger' died ServiceManager: service 'media.player' died ServiceManager: service 'media.camera' died ServiceManager: service 'android.security.keystore' died Cryptfs : unmounting /data failed Bug: 17576594
-
Jeff Sharkey authored
This will help us track down who requested a data wipe. Bug: 17412160 Change-Id: I5ab39a4de03c973ed151d703d6462a172ee043fd
-
- 23 Sep, 2014 1 commit
-
-
Paul Lawrence authored
* commit '3846be17': Reduce cryptfs logspam
-
- 22 Sep, 2014 1 commit
-
-
Paul Lawrence authored
Bug: 17572886 Change-Id: I91302ccc284e0f908299852650db5bf645f2ff71
-
- 19 Sep, 2014 2 commits
-
-
Alex Klyubin authored
* commit '6efa9351': Don't use deprecated OpenSSL functions.
-
Alex Klyubin authored
-
- 12 Sep, 2014 5 commits
-
-
Paul Lawrence authored
* commit '8e3f4510': HACK: Retry/reboot when mount reports busy.
-
Dan Albert authored
Change-Id: I224499833777ef80d85c1199f475f5ed1568d053
-
Dan Albert authored
-
Paul Lawrence authored
This is a hack because we don't know why mount() reports busy. Requires dependent change in syste/core: https://googleplex-android-review.git.corp.google.com/#/c/543125/ Bug: 17358530 Change-Id: I8d3078bc68f8c450adce2c3a4101b6a958f1c4a0
-
Dan Albert authored
Don't manually include stlport, and don't use private bionic headers. Change-Id: I44dd212fdd5874e625890c548e9d7bf3a9c27912
-
- 10 Sep, 2014 1 commit
-
-
Paul Lawrence authored
* commit '7e17e2d2': Don't worry about battery levels when encrypting
-