- 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
-
- 11 Apr, 2015 1 commit
-
-
Jeff Sharkey authored
Sadly setexeccon() is process global, so we need to carefully ensure that all exec() are mutually exclusive to avoid transitioning into unwanted domains. Also, because we have several threads floating around, we need to guard all our FDs with O_CLOEXEC. Format all newly created volumes immediately after partitioning, but silence all events emitted from those volumes to prevent the framework from getting all excited. Unify all notify events under a single codepath to make them easy to silence. Sent SIGINT before escalating to SIGTERM when unmounting. Bug: 19993667 Change-Id: Idc6c806afc7919a004a93e2240b42884f6b52d6b
-
- 01 Apr, 2015 1 commit
-
-
Jeff Sharkey authored
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
-
- 30 Mar, 2015 1 commit
-
-
Hiroaki Miyazawa authored
ioctl(BLKGETSIZE) expects unsigned long (8 bytes on 64 bit environment). This is fixing fails in android.os.storage.StorageManagerIntegrationTest (in FrameworkCoreTests). To verify, install FrameworksCoreTests.apk and do: adb shell am instrument -r -w -e class android.os.storage.\ StorageManagerIntegrationTest#testMountSingleEncryptedObb \ com.android.frameworks.coretests/android.test.InstrumentationTestRunner Change-Id: Ib6d5c7490c02521c93f107c35ad0aac49f6a3f1a
-
- 18 Dec, 2014 1 commit
-
-
Tim Murray authored
-Wno-missing-field-initializers is used as well, but that is an overzealous warning from initializing structs with {0} and not a real warning. bug 18736778 and 16868177 Change-Id: Iffde89cd7200d9a11193e1614f1819f9fcace30a
-
- 16 Jul, 2014 1 commit
-
-
Daniel Rosenberg authored
Updated cluster size to be 32k, and aligned the starting cluster of the root directory to be cluster aligned. Change-Id: I759997569f7a0263a076cc462b235a6cf54e0c5f Signed-off-by:
Daniel Rosenberg <drosen@google.com>
-
- 13 Jun, 2013 1 commit
-
-
Ken Sumrall authored
The new wipe option to the vold format command will invoke BLKDISCARD on the partition before invoking newfs_msdos. This will be used whenever a full wipe of the device is wanted, as this is more secure than just doing newfs_msdos. Bug: 9392982 Change-Id: Ie106f1b9cc70abc61206006d1821641c27c7ccae
-
- 10 Feb, 2013 1 commit
-
-
Chih-Wei Huang authored
The patch removes the following warnings: system/vold/vdc.c: In function 'do_cmd': system/vold/vdc.c:71:17: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] [...] In file included from system/vold/Fat.cpp:34:0: bionic/libc/kernel/common/linux/fs.h:109:0: warning: "MS_RMT_MASK" redefined [enabled by default] In file included from system/vold/Fat.cpp:31:0: bionic/libc/include/sys/mount.h:64:0: note: this is the location of the previous definition [...] Change-Id: I1e950dcec87f8bae0cec61a1611126b3abc0c90e
-
- 30 Jan, 2013 1 commit
-
-
Rom Lemarchand authored
Use liblogwrap to provide logwrapper functionality instead of using vold's own implementation. Change-Id: I76aac5aa72a1fdca043a63b86c6a9b54e7abec16
-
- 04 Jan, 2013 1 commit
-
-
Rom Lemarchand authored
Make sure all the calls to logwrap are consistent with the function's semantics. Change-Id: Ib0e2ad5c283cc4bb06c0ef5d6a9a52a5840b3dd2
-
- 16 Nov, 2010 1 commit
-
-
Olivier Bailly authored
Change-Id: I9f71b5e871671d1d64ad37f78a8944653409b8e1
-
- 02 Sep, 2010 1 commit
-
-
Kenny Root authored
This allows us to place shared libraries in these containers which may only be loaded if they are executable. Change-Id: I78fa9ab6d5c58ec8b98c40004da72aebc0aade2a
-
- 25 Mar, 2010 1 commit
-
-
San Mehat authored
Change-Id: I48ee8bd90b47f5845f069cdf4d1b8ba6ecdb1b39 Signed-off-by:
San Mehat <san@google.com>
-
- 03 Mar, 2010 1 commit
-
-
San Mehat authored
Add an un-encrypted superblock to the end of a secure container to help identify the crypto cipher used. This is required in order to provide some semblence of versioning, in case we have cause to change the crypto type on an update - say for example switching from software to hardware encryption, or from 128 -> a zillion bit keys. NOTE: This format is incompatible with previous secure containers. After this change they will no longer be mountable. Signed-off-by:
San Mehat <san@google.com>
-
- 08 Feb, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 04 Feb, 2010 1 commit
-
-
San Mehat authored
- share command was taking wrong arguments - shared command was returning two termination codes - Force FAT32 cluster size to 4k when formatting Signed-off-by:
San Mehat <san@google.com>
-
- 09 Jan, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 07 Jan, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 06 Jan, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-
- 04 Jan, 2010 1 commit
-
-
San Mehat authored
Signed-off-by:
San Mehat <san@google.com>
-