Commit Graph

931 Commits

Author SHA1 Message Date
Michael Runge
f15e31edf9 Log mount/unmount errors to UI
Bug: 18092022
Change-Id: I6c42038ebeb1cfc1e7ca0d3e12310fdce1b990b0
2014-10-24 16:05:13 -07:00
Nick Kralevich
6a821fe5f0 unconditionally apply SELinux labels to symlinks
At the end of the OTA script, we walk through /system, updating
all the permissions on the filesystem, including the UID, GID,
standard UNIX permissions, capabilities, and SELinux labels.

In the case of a symbolic link, however, we want to skip most of
those operations. The UID, GID, UNIX permissions, and capabilities
don't meaningfully apply to symbolic links.

However, that's not true with SELinux labels. The SELinux label on
a symbolic link is important. We need to make sure the label on the
symbolic link is always updated, even if none of the other attributes
are updated.

This change unconditionally updates the SELinux label on the symbolic
link itself. lsetfilecon() is used, so that the link itself is updated,
not what it's pointing to.

In addition, drop the ENOTSUP special case. SELinux has been a
requirement since Android 4.4. Running without filesystem extended
attributes is no longer supported, and we shouldn't even try to handle
non-SELinux updates anymore. (Note: this could be problematic if
these scripts are ever used to produce OTA images for 4.2 devices)

Bug: 18079773
Change-Id: I87f99a1c88fe02bb2914f1884cac23ce1b385f91
2014-10-24 16:05:13 -07:00
Michael Runge
bd6138cffe Allow passing of mount args to mountFn
Bug: 18079773
Bug: 18092222

Change-Id: Ifc3f3e123de729dfbb2f49414b3207afa96268d5
2014-10-23 17:35:13 -07:00
Michael Runge
7548025bdd Log to UI any metadata setting errors
Bug: 18079773
Change-Id: Ic6fddbcbcb6ddb9e1cbd1698df98387c0033ae15
2014-10-23 17:35:13 -07:00
Nick Kralevich
b8344b6f59 Make /cache/recovery/last_log available in recovery
Create a new recovery UI option to allow the user to view
/cache/recovery/last_log for their device. This gives enhanced
debugging information which may be necessary when a failed
OTA occurs.

Bug: 18094012
Change-Id: Ic3228de96e9bfc2a0141c7aab4ce392a38140cf3
2014-10-23 17:35:13 -07:00
Michael Runge
d5b1727765 Treat already-renamed files as having no problems.
This should help with reentrant OTAs.

Bug: 18079773

Change-Id: I102fd738e3b450483ecd4471384c12e89fc586e2
2014-10-22 17:44:33 -07:00
The Android Automerger
6dcd119446 merge in lmp-release history after reset to a6e13ae01b 2014-10-21 17:42:57 -07:00
The Android Automerger
e55d0326c4 merge in lmp-release history after reset to a6e13ae01b 2014-10-21 06:09:31 -07:00
The Android Automerger
b57de6082a merge in lmp-release history after reset to a6e13ae01b 2014-10-19 17:07:49 -07:00
The Android Automerger
a238104904 merge in lmp-release history after reset to a6e13ae01b 2014-10-16 06:09:42 -07:00
The Android Automerger
3648601635 merge in lmp-release history after reset to a6e13ae01b 2014-10-15 06:09:28 -07:00
The Android Automerger
c6aafd42da merge in lmp-release history after reset to a6e13ae01b 2014-10-14 06:09:29 -07:00
The Android Automerger
078bd94187 merge in lmp-release history after reset to a6e13ae01b 2014-10-13 06:09:28 -07:00
The Android Automerger
66b01fb51c merge in lmp-release history after reset to a6e13ae01b 2014-10-12 06:09:32 -07:00
The Android Automerger
b7f9825603 merge in lmp-release history after reset to a6e13ae01b 2014-10-09 06:09:27 -07:00
The Android Automerger
dc5206cbb5 merge in lmp-release history after reset to a6e13ae01b 2014-10-08 06:10:37 -07:00
The Android Automerger
f51aa2794a merge in lmp-release history after reset to a6e13ae01b 2014-10-07 06:09:30 -07:00
The Android Automerger
7d393c5a32 merge in lmp-release history after reset to a6e13ae01b 2014-10-06 06:10:15 -07:00
The Android Automerger
39d267741d merge in lmp-release history after reset to a6e13ae01b 2014-10-05 06:10:04 -07:00
The Android Automerger
a7aaeee986 merge in lmp-release history after reset to a6e13ae01b 2014-10-01 06:10:47 -07:00
The Android Automerger
427df77146 merge in lmp-release history after reset to a6e13ae01b 2014-09-30 06:11:46 -07:00
The Android Automerger
1986e9e6aa merge in lmp-release history after reset to a6e13ae01b 2014-09-29 06:11:31 -07:00
The Android Automerger
8e76df9660 merge in lmp-release history after reset to a6e13ae01b 2014-09-28 06:10:04 -07:00
The Android Automerger
c855022536 merge in lmp-release history after reset to a6e13ae01b 2014-09-25 06:11:55 -07:00
Jeff Sharkey
a6e13ae01b Include reason when wiping data.
This will help us track down who requested a data wipe.

Bug: 17412160
Change-Id: I1c439fbd29f96b9851810baca9101f683a0f18d8
2014-09-24 11:46:17 -07:00
The Android Automerger
96e3b4f2af merge in lmp-release history after reset to 574443d895 2014-09-24 06:10:53 -07:00
The Android Automerger
98faabce41 merge in lmp-release history after reset to 574443d895 2014-09-23 06:10:54 -07:00
The Android Automerger
8e54f2fad8 merge in lmp-release history after reset to 574443d895 2014-09-22 06:10:07 -07:00
The Android Automerger
07159ef96d merge in lmp-release history after reset to 574443d895 2014-09-21 06:09:23 -07:00
The Android Automerger
9e7c34c4bd merge in lmp-release history after reset to 6241a16695 2014-09-20 21:00:37 -07:00
The Android Automerger
becf1e799b merge in lmp-release history after reset to 574443d895 2014-09-20 06:09:47 -07:00
The Android Automerger
6241a16695 merge in lmp-release history after reset to 574443d895 2014-09-18 06:09:14 -07:00
The Android Automerger
7facb691ed merge in lmp-release history after reset to 574443d895 2014-09-17 06:09:58 -07:00
The Android Automerger
4954d8a1fd merge in lmp-release history after reset to 574443d895 2014-09-16 06:09:54 -07:00
The Android Automerger
a160ad7ef6 merge in lmp-release history after reset to 574443d895 2014-09-15 06:09:48 -07:00
The Android Automerger
4cd02aeaeb merge in lmp-release history after reset to 574443d895 2014-09-14 06:09:36 -07:00
The Android Automerger
c02b9ef11f merge in lmp-release history after reset to 5e238a9971 2014-09-13 08:42:01 -07:00
The Android Automerger
9bcc1875c0 merge in lmp-release history after reset to 574443d895 2014-09-13 06:09:54 -07:00
The Android Automerger
5e238a9971 merge in lmp-release history after reset to 574443d895 2014-09-11 06:09:10 -07:00
The Android Automerger
f6eb389525 merge in lmp-release history after reset to 574443d895 2014-09-10 06:09:16 -07:00
The Android Automerger
4fc827e933 merge in lmp-release history after reset to 574443d895 2014-09-09 06:09:24 -07:00
The Android Automerger
9c574d1d2a merge in lmp-release history after reset to 574443d895 2014-09-08 06:09:43 -07:00
The Android Automerger
500c1fb27c merge in lmp-release history after reset to 574443d895 2014-09-07 06:08:57 -07:00
The Android Automerger
c398172f94 merge in lmp-release history after reset to f9bc2a544d 2014-09-06 08:50:41 -07:00
The Android Automerger
9132bd040b merge in lmp-release history after reset to 574443d895 2014-09-06 06:08:47 -07:00
Doug Zongker
f9bc2a544d create block map for all update packages on /data
Always create the block map for packages on /data; don't only look at
the encryptable/encrypted flags.

Bug: 17395453
Change-Id: Iaa7643a32898328277841e324305b9419a9e071c
2014-09-05 13:06:47 -07:00
Doug Zongker
574443d895 create block map for all update packages on /data
Always create the block map for packages on /data; don't only look at
the encryptable/encrypted flags.

Bug: 17395453
Change-Id: Iaa7643a32898328277841e324305b9419a9e071c
2014-09-05 08:22:12 -07:00
Doug Zongker
40482ea2ae Merge "fix comment in blockimg updater code" into lmp-dev 2014-09-04 15:26:29 +00:00
Doug Zongker
f7bb09dae8 fix comment in blockimg updater code
The comment for the DEBUG_ERASE setting is exactly backwards.

Change-Id: I98ab5828365894217fc78976817a131e7d22d5c1
2014-09-04 08:10:32 -07:00
Andrew Boie
8328922ff0 use lseek64 instead of lseek
Otherwise, overflow problems can occur with images larger than
2G since the offsets will overflow a 32-bit off_t.

Change-Id: I05951a38ebeae83ad2cb938594e8d8adb323e2aa
Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2014-09-04 07:54:17 -07:00