Skip to content

GitLab

Switch branch/tag
  1. 10 Jul, 2015 1 commit
    • Thierry Strudel's avatar
      fs_config: replace getenv('OUT') by new fs_config parameter · df33ffad
      Thierry Strudel authored 
      
Using a getenv('OUT') in such a deep down function is a wrong design
choice. Replacing with explicit parameter that may be NULL in case
device specific files can be accessed from /.
Since TARGET_COPY_OUT_SYSTEM may be defined to something different than
system we also ensure that we use a path relative to TARGET_OUT to
compute path to fs_config_* files.

Bug: 21989305
Bug: 22048934
Change-Id: Id91bc183b29beac7379d1117ad83bd3346e6897b
Signed-off-by: default avatarThierry Strudel <tstrudel@google.com>
      df33ffad
  3. 08 Jul, 2015 1 commit
    • Sami Tolvanen's avatar
      fs_mgr: Use ro.boot.veritymode · 3fd58ae7
      Sami Tolvanen authored 
      If verity state is managed by bootloader, it will pass the verity
mode to the kernel in the androidboot.veritymode command line
parameter. Init copies the value to the ro.boot.veritymode property.

Check for ro.boot.veritymode in fs_mgr and use the value to set
dm-verity mode. If this property is not set, store verity state in
metadata as before, if a storage location is specified in fstab.

Bug: 21605676
Change-Id: Ife3c978c133248432c302583d3b70e179605fe42
(cherry picked from commit ac5c1224)
      3fd58ae7
  5. 29 May, 2015 1 commit
  7. 27 May, 2015 1 commit
  9. 02 May, 2015 1 commit
  11. 24 Apr, 2015 1 commit
  13. 10 Apr, 2015 1 commit
    • Chris Fries's avatar
      fs_mgr: introduce fs_mgr_format to format wiped partitions · 79f33846
      Chris Fries authored 
      Move fastboot's format logic into fs_mgr, to consolidate the knowledge
about how to do this (and when to wipe metadata).

Try to format these formattable paritions if they are wiped.

If formatting fails, we will fall out to let recovery mode handle it.

Bug: 20082763
Change-Id: I397cc197550e78d932e8a154fd234695c46dbe7b
      79f33846
  15. 09 Apr, 2015 1 commit
  17. 08 Apr, 2015 1 commit
  19. 06 Apr, 2015 1 commit
  21. 01 Apr, 2015 2 commits
  23. 31 Mar, 2015 3 commits
  25. 26 Mar, 2015 2 commits
    • Paul Lawrence's avatar
      Revert "Adding e4crypt support" · 84b0bab5
      Paul Lawrence authored 
      This reverts commit 6095afc1.

Change-Id: Icedfe0036223d7f42eaaefc4a35ad0f2efb14e4e
      84b0bab5
    • Sami Tolvanen's avatar
      Fix build · 4d3ead9d
      Sami Tolvanen authored 
      Fix build breakage in aosp_fugu-userdebug_clang (linux) caused
by Id8711f7d51dc1e4e9a4d84f9951240f64528e69d

Change-Id: Icd04aeaf131be045cf5788846ae9832e6cbbb944
      4d3ead9d
  27. 24 Mar, 2015 1 commit
    • Sami Tolvanen's avatar
      Use structured format for verity metadata · 946a0f3e
      Sami Tolvanen authored 
      Specify the location of verity metadata in fstab, and use a
type-length-value format for the metadata that allows other
data to be stored in the same location in an extensible way.

Change-Id: Id8711f7d51dc1e4e9a4d84f9951240f64528e69d
      946a0f3e
  29. 23 Mar, 2015 1 commit
  31. 19 Mar, 2015 1 commit
    • Sami Tolvanen's avatar
      Add init command to set verified properties · acbf9bef
      Sami Tolvanen authored 
      Add a command that updates dm-verity state and sets partition.%.verified
properties used by adb remount.

This is needed in init since fs_mgr cannot set properties:
    I6a28cccb1ccce960841af20a4b20c32d424b5524

Change-Id: I0fdf5bc29c56690dcadff9d0eb216d3c68483538
      acbf9bef
  33. 06 Mar, 2015 1 commit
  35. 05 Mar, 2015 1 commit
    • Sami Tolvanen's avatar
      Do not call libcutils property_set in init through libfs_mgr · 86cddf40
      Sami Tolvanen authored 
      Both init and libcutils define a property_set function. The init
version sets the property directly while libcutils simply calls
__system_property_set, which sends a message to init to set the
property.

Since libfs_mgr is statically linked to libcutils, any calls to
property_set end up sending a message to init and waiting for a
response. When libfs_mgr is further statically linked to init,
this leads to init sending a message to itself when property_set
is called in fs_mgr.

Because send_prop_msg in bionic only waits for a response for
250ms, this does not cause a deadlock. However, using libcutils
to set a property in the init process is hardly a good idea.

This change removes the property_set call from fs_mgr_verity.c.
If this property is required later, it should be set elsewhere.

Change-Id: I6a28cccb1ccce960841af20a4b20c32d424b5524
      86cddf40
  37. 04 Mar, 2015 2 commits
    • Andreas Gampe's avatar
      Fs_mgr: Fix format code · eb69e857
      Andreas Gampe authored 
      Suggested printing for off_t is to cast to intmax_t and print that.

Follow-up to https://android-review.googlesource.com/133111.

Change-Id: Icff6844044c3d0fa6372c3f399453a526fd89954
      eb69e857
    • Sami Tolvanen's avatar
      Add fs_mgr support for dm-verity modes · 51bf11ad
      Sami Tolvanen authored 
      Add support for dm-verity modes and storing persistent state in
a location specified by the following properties:

  ro.verity.state.location
  ro.verity.state.offset

If these properties do not exist, dm-verity is always loaded in
EIO mode. If the properties do exist, but the location does not
have valid state data, dm-verity is loaded in RESTART mode. The
mode is updated to LOGGING if a dm-verity triggered restart has
occurred.

Change-Id: Ibb82953594d234f81ad21c40f524190b88e4ac8f
      51bf11ad
  39. 27 Feb, 2015 1 commit
    • Sami Tolvanen's avatar
      Set underlying block device RO when enabling verity · 214f33b8
      Sami Tolvanen authored 
      Currently, when verity is set up on a block device, the underlying
device is still accessible directly. Change the existing function
fs_set_blk_ro visible to other fs_mgr modules, change the behavior
to match the comment above the function definition, and call it to
disable write access to the block device when setting up verity.

Bug: 18609347
Change-Id: I7884175df15f9161174788d74d20a08e4cd472ca
      214f33b8
  41. 18 Feb, 2015 1 commit
  43. 06 Feb, 2015 2 commits
    • Paul Lawrence's avatar
      Revert "Make encryption configurable" · 317b4024
      Paul Lawrence authored 
      This reverts commit bda62724.

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
      317b4024
    • Nick Kralevich's avatar
      fs_mgr: error check umount calls / add retry logic · 7294eb6c
      Nick Kralevich authored 
      Don't silently ignore umount errors. At a minimum, log them.

Add strerror(errno) to another umount call, to make sure we get
some actionable data.

check_fs: try 5 times umounting the filesystem. It appears that
the umount is failing, perhaps because some service is opening
the file on the device or other error. Try unmounting it multiple
times in case it's a transient problem and we can recover.

Bug: 19199624
Bug: 19156134
Change-Id: I7213eb52d55116fb2419a36494d26d5e159981a7
      7294eb6c
  45. 28 Jan, 2015 2 commits
  47. 23 Jan, 2015 2 commits
  49. 21 Jan, 2015 1 commit
  51. 17 Jan, 2015 1 commit
    • Christoffer Dall's avatar
      fs_mgr: Support filesystem labels in fstab · 69407ccb
      Christoffer Dall authored 
      
When mounting fstab entries it is practical to be able to specify
for example LABEL=data instead of a specific block device.

This is particularly important for the new Android Emulator code base,
which uses virtio block devices for the various partitions
(system,data,cache), because there is no defined ordering between the
way the filesystems are specified to the emulator and how they are
enumerated by the android kernel as /dev/vdX.

Change-Id: I12c3db0ba6a515dc8e917e0349afd257888d3aef
Signed-off-by: default avatarChristoffer Dall <christoffer.dall@linaro.org>
      69407ccb
  53. 07 Jan, 2015 1 commit
  55. 10 Dec, 2014 3 commits
  57. 13 Nov, 2014 2 commits