| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Transitioning devices may have the context option present in the
fstab, even if we're not doing selinux builds.
Since we don't set or even create the contexts on those builds,
this will make mount fail, and either the mountpoint ends up absent,
or boot fails entirely
Change-Id: Ic5cc7f5632cc3d62459dfaaf7719d662737e1641
|
|
|
|
|
|
|
|
| |
This reverts commit 806fc566fd4544cfcd3334aa1a992bab0f6d277c.
Revert "fs_mgr: Don't assume all fstab entries have options"
This reverts commit a73b2264dfd89d526054e4be9926be9f50cca791.
|
|
|
|
| |
Change-Id: I5f537b09d96efa2758372f9da6d66996c2164ee8
|
|
|
|
|
|
|
| |
This will require that transitioning devices have context as the
last mount option, since everything after it will be ignored
Change-Id: Ic5cc7f5632cc3d62459dfaaf7719d662737e1641
|
|
|
|
| |
Change-Id: Ie220f5cb7b614a48ec8afe66f4721ede3a368166
|
|
|
|
|
| |
Bug: 6925012
Change-Id: Id8d887d17c6b1b2f90cfd1a1de991ccaba730b7d
|
|
|
|
|
|
|
| |
This works around a performance problem in the firmware of
some emmc chips.
Change-Id: Ia414b4604d11e47ce9cb3f86ac82602e081bb09e
|
|
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
|