diff options
| author | Mark Salyzyn <salyzyn@google.com> | 2018-11-20 12:59:21 -0800 |
|---|---|---|
| committer | Mark Salyzyn <salyzyn@google.com> | 2018-11-27 13:46:55 -0800 |
| commit | cb2f6b6776469f167eacdc2d6c38c1e5f1619b33 (patch) | |
| tree | 780ddbae8c2c75e2807fb416f95a9e8621736046 /libunwindstack/tests/MemoryFileTest.cpp | |
| parent | fa105049d886018bb4d068986b935368f39ff1c2 (diff) | |
fs_mgr: overlayfs: resize scratch should it be too small
If scratch gets made too small (eg: fastboot flash scratch small-file)
it can not recover without a workaround. The workaround is not
intuitive, (adb enable-verity then adb disable-verity to erase and
re-establish the proper sized scratch. This needs to be automatic.
If we detect it is too small to support a filesystem, resize it to an
more appropriate size if it exists.
Alter unit test to check for fastboot characteristics and assumptions
associated with the scratch partition, and a test case to flash the
partition.
Test: adb-remount-test.sh
Bug: 109821005
Change-Id: Icfceaa461c2bf13ca5a7dd4e34675dde8a4d251f
Diffstat (limited to 'libunwindstack/tests/MemoryFileTest.cpp')
0 files changed, 0 insertions, 0 deletions