tree ae85f89451ef4e278cd237f4a2b28686c2f043c1
parent 00807f5ab9f53c48f05319d8510aa41be0ba6ea7
author Brad Fitzpatrick <bradfitz@android.com> 1283209276 -0700
committer Brad Fitzpatrick <bradfitz@android.com> 1283285809 -0700

Don't propagate StrictMode over one-way Binder calls.

This was causing stack stitching problems where a one-way call with
violations followed by a two-way call without violations was getting
the previous one-way call's violation stack stitched on to the second
caller's stack.

The solution is a little more indirect than I would've liked
(preserving the binder's onTransact flags until enforceInterface) but
was seemingly necessary to work without changing the AIDL compiler.
It should also be sufficiently cheap, since no new calls to
thread-local IPCThreadState lookups were required.  The additional
work is just same-thread getter/setters on the existing
IPCThreadState.

Change-Id: I4b6db1d445c56e868e6d0d7be3ba6849f4ef23ae