tree 898231a189fb42ae3b64299120e903e443d7d694
parent 9690e2b370f3f303ef75e1fd5c7fdbea8787d46a
author Alistair Strachan <alistair.strachan@imgtec.com> 1374082909 -0700
committer Doug Zongker <dougz@android.com> 1384797166 -0800

Restore default umask after forking for update-binary.

A system/core change made in Mar 26 2012 6ebf12f "init: Change umask
of forked processes to 077" changed the default umask of services
forked from init.

Because recovery is forked from init, it has a umask of 077. Therefore
when update-binary is forked from recovery, it too has a umask of 077.

This umask is overly restrictive and can cause problems for scripts
relying on minzip to extract binaries directly into the target
filesystem. Any directories updated by minzip will have their
permissions reset to r-x------ and created files will have similarly
restrictive permissions.

As it seems unlikely this security measure was intended to have this
side effect on legacy sideloads that do not have chmods to repair
the damage done by minzip, this change reverts the umask to 022 in
the fork made for update-binary.

Change-Id: Ib1a3fc83aa4ecc7480b5d0c00f3c7d0d040d4887