merge in klp-release history after reset to klp-dev
Add flock(2)ing on dex-cache files to prevent races

Bug: 9071417
Change-Id: I1ee9ff281867f90fba7a8ed8bbf06b33ac29d511
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
Fix ImageHeader.IsValid

Change-Id: Ia56f4ded63a726a416225bf4a536175aa435866e
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
Revert "Fix CAS intrinsic to clear exclusive if values don't match."

Ian is correct. I can still see this bug even with this change.

This reverts commit 3a0831507637028a439712dedaaddd7cd0893995.

Change-Id: I780f2de926f1ff7576adc679c56a6cf491dad127
Make inlined CAS32 loop until store is successful if values match.

The native implementation of compareAndSwap uses android_atomic_cas,
which will repeat the strex until it succeeds. The compiled version
was changed to do the same.

Bug: 10530407
Change-Id: I7efb3f92d0d0610fcc5a885e2c97f1d701b5a4ea
(cherry picked from commit 2de2aa1a96dfa5bebc004f29b5dbfafd37039cee)
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev
merge in klp-release history after reset to klp-dev