| 317b4024a2a46b8c57abfa08f2a649df13572bd3 |
|
06-Feb-2015 |
Paul Lawrence <paullawrence@google.com> |
Revert "Make encryption configurable"
This reverts commit bda6272446454886339841a62daaa1b66c07ad60.
The original fix seems to have led to boot failures in QA. Rather than
risk shipping, revert the change. Bug 18764230 reopened.
Requires change
https://googleplex-android-review.git.corp.google.com/#/c/629764/
Bug: 19278390
Bug: 19199624
Change-Id: I8b6ab585666f2b0f585ffb2a5f61ac2e3462e06e
/system/core/fs_mgr/include/fs_mgr.h
|
| bda6272446454886339841a62daaa1b66c07ad60 |
|
21-Jan-2015 |
Paul Lawrence <paullawrence@google.com> |
Make encryption configurable
Delay mounting encryptable but unencrypted volumes until we can
check the ro.vold.forceencrypt flag, then optionally encrypt.
Requires matching vold change from
https://googleplex-android-review.git.corp.google.com/#/c/615309/
Bug: 18764230
Change-Id: If22008be8de6a4f3216b349f81ace49be1730314
/system/core/fs_mgr/include/fs_mgr.h
|
| bbb36319119edde9377fb80015235893c30d2bc9 |
|
09-Oct-2014 |
Paul Lawrence <paullawrence@google.com> |
Revert "Revert "Enable verity on userdebug, and add disable-verity to adb""
This reverts commit 152d2d4234ba89e0c20c4af13e291b6049a7bc33.
Fixed build error, and also fixed memory leak spotted from warning.
Bug: 17691572
Change-Id: I23b5ba537f7b557432041d4338b38b9be434e981
/system/core/fs_mgr/include/fs_mgr.h
|
| 152d2d4234ba89e0c20c4af13e291b6049a7bc33 |
|
09-Oct-2014 |
Nick Kralevich <nnk@google.com> |
Revert "Enable verity on userdebug, and add disable-verity to adb"
Build is broken.
system/core/fs_mgr/fs_mgr_verity.c: In function 'fs_mgr_setup_verity':
system/core/fs_mgr/fs_mgr_verity.c:103:20: error: 'verity_table_signature' may be used uninitialized in this function [-Werror=maybe-uninitialized]
if (!RSA_verify(key,
^
system/core/fs_mgr/fs_mgr_verity.c:374:11: note: 'verity_table_signature' was declared here
char *verity_table_signature;
^
cc1: all warnings being treated as errors
make: *** [out/target/product/minnow/obj/STATIC_LIBRARIES/libfs_mgr_intermediates/fs_mgr_verity.o] Error 1
make: *** Waiting for unfinished jobs....
This reverts commit d4cea0bc16d1ad96cc6d6177232d7b339785460c.
Change-Id: I6862cc79ef9d944a2472b6fb2e46dae514cea8ce
/system/core/fs_mgr/include/fs_mgr.h
|
| d4cea0bc16d1ad96cc6d6177232d7b339785460c |
|
07-Oct-2014 |
Paul Lawrence <paullawrence@google.com> |
Enable verity on userdebug, and add disable-verity to adb
Bug: 17691572
Change-Id: I58f588f318e7952d06a41325337d946d7c007e31
/system/core/fs_mgr/include/fs_mgr.h
|
| cf234dc7e081ac4063c3c5ddcdd4da40c82d51cb |
|
09-Sep-2014 |
Paul Lawrence <paullawrence@google.com> |
Preserve errno from fsmgr_do_mount
Bug: 17358530
Change-Id: I4cd7403c0b7c4f878d6afa5199f998e6f614adb9
/system/core/fs_mgr/include/fs_mgr.h
|
| cee206880ef80ac570df6b369d12f111c00f653a |
|
02-Jul-2014 |
JP Abgrall <jpa@google.com> |
[HACK]fs_mgr+init: Format via recovery if encryptable /data is wiped
If the encryptable partition is wiped (4KB worth of 0 or 0xff),
then reboot into recovery to format /data+/cache
This is while waiting for the Mac OS support to format f2fs.
The flashstation running on Mac OS will currently just erase userdata
and not format it with f2fs.
Bug: 15720406
Bug: 15747366
Change-Id: Ib7cca3e1701483a09573457a835750f34da71ee0
/system/core/fs_mgr/include/fs_mgr.h
|
| f22b7452940c99b830749cabdd929f9f7cfdaacc |
|
02-Jul-2014 |
JP Abgrall <jpa@google.com> |
fs_mrg: clean up multi-type mount_all
Move the code that attempts to mount alternative fstab entries
into its own function.
Clarify return codes.
Suggest wipe via recovery in error messages.
Bug: 15747366
Change-Id: I3634477cd4d1d73f974f3e906c53285f0d9e0eac
Signed-off-by: JP Abgrall <jpa@google.com>
/system/core/fs_mgr/include/fs_mgr.h
|
| 5c01dac6d81a804dcff233da777882bec852f25b |
|
18-Jun-2014 |
JP Abgrall <jpa@google.com> |
fsmgr: support multiple fs-types/mountpoint
Previous attempt was broken.
It would incorrectly be affected by mount failures.
This changes allows an fstab to contain multiple lines for a given
mount point.
The lines sharing a mount MUST be after each other.
The 1st matching line is the primary when it comes to mounting
and look ups for wiping.
Mounting based on a mount_point will attempt each dup in turn
until one succeeds.
The reported error will be that of the last failed attempt.
This is to allow quick experimentation between different FSes.
Bug: 15702546
Change-Id: I378d68ad13eb0098ec1ccb8dcf108b82acbe9ebb
Signed-off-by: JP Abgrall <jpa@google.com>
/system/core/fs_mgr/include/fs_mgr.h
|
| f786fe54388cb4461f8e13845ca6a1df0d2e1236 |
|
18-Jun-2014 |
JP Abgrall <jpa@google.com> |
fsmgr: revert multiple fs-types/mountpoint (fix N5 boot)
This is apparently breaking N5, so reverting for now.
This reverts commit a794f86522f9125f2547c94ebc7c74d1e7ace013.
Bug: 15709256
Change-Id: I37a5160eead17e153e2c83fa94632ffa5d8553c2
/system/core/fs_mgr/include/fs_mgr.h
|
| a794f86522f9125f2547c94ebc7c74d1e7ace013 |
|
18-Jun-2014 |
JP Abgrall <jpa@google.com> |
fsmgr: allow for a multiple fs-types for a mount point.
This changes allows an fstab to contain multiple lines for a given
mount point.
The lines sharing a mount MUST be after each other.
The 1st matching line is the primary when it comes to mounting
and look ups for wiping.
Mounting based on a mount_point will attempt each dup in turn
until one succeeds.
This is to allow quick experimentations between different FSes.
It does not deal with checkfs yet, because the underlying invocation
of fs-type appropriate fsck does not handle the error code.
Only the primary FS (1st in the dups) is checked.
Change-Id: I8329737454b53e2681436fe85cd00a9bc522676b
Signed-off-by: JP Abgrall <jpa@google.com>
/system/core/fs_mgr/include/fs_mgr.h
|
| cdc1cfb3e51f3caddc1f290b46dc789c036f22ed |
|
11-Apr-2014 |
Sasha Levitskiy <sanek@google.com> |
Cleanup: warning fixit.
bootable/recovery has a dependent commit: I9adb470b04e4301989d128c9c3097b21b4dea431
Change-Id: Icf23e659265d71d5226d527c2b40cfbc132320ee
Signed-off-by: Sasha Levitskiy <sanek@google.com>
/system/core/fs_mgr/include/fs_mgr.h
|
| 887f2892062c64fa688fc9525ebd09cc98ca70d8 |
|
12-Sep-2013 |
Ken Sumrall <ksumrall@android.com> |
New fstab flags to support more expressive SD card permissions
Bug: 10330128
Change-Id: I41fb178b839487b604762fbc1ccba097d25c7aa0
/system/core/fs_mgr/include/fs_mgr.h
|
| 3ad3d1c4b5856d4e314febc5671c74e78a76db00 |
|
23-Feb-2013 |
Geremy Condra <gcondra@google.com> |
Add basic verity support to fs_mgr.
This change adds a "verify" fs_mgr flag specifying that
the device in question should be verified.
Devices marked with this flag are expected to have a
footer immediately after their data containing all
the information needed to set up a verity instance.
Change-Id: I10101f2c3240228ee0932e3767fe35e673d2e720
/system/core/fs_mgr/include/fs_mgr.h
|
| 5bc31a2632f453e03edac714b865773970bba608 |
|
09-Jul-2013 |
Ken Sumrall <ksumrall@android.com> |
Add support for swap entries in fstab
Swap entries can optionally specify a swapprio= or zramsize= flag
in the fs_mgr flags field.
Change-Id: I30530501efd4112af4e158898a9f65f6443c4fdb
/system/core/fs_mgr/include/fs_mgr.h
|
| ab6b852235d99d752678312c155a3f1c140fb483 |
|
13-Feb-2013 |
Ken Sumrall <ksumrall@android.com> |
fs_mgr: support a unified fstab format.
Update fs_mgr to support more flags needed to unify the 3
fstabs currently in android into one.
Change-Id: Ie46cea61a5b19882c55098bdd70f39e78fb603be
/system/core/fs_mgr/include/fs_mgr.h
|
| 7574c035b2dcf8316c562c648113be6be65cb061 |
|
07-Jan-2012 |
Ken Sumrall <ksumrall@android.com> |
A filesystem manager library to mount filesystems for init.
Instead of specifying in init what to mount, and having various hacks in init
itself to deal with encryption, use a filesystem manager library to do the
work, that can also be invoked by vold when mounting an encrypted volume.
Keep all the magic filesystem info an a device specific fstab file.
Change-Id: Ib988f1e4fb0638ba1d5fd98407fa6d8cf862aaca
/system/core/fs_mgr/include/fs_mgr.h
|