Brad Fitzpatrick 5273603e98 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		2010-08-31 13:16:49 -07:00
..
Android.mk
Binder.cpp
BpBinder.cpp
IInterface.cpp
IMemory.cpp
IPCThreadState.cpp	Don't propagate StrictMode over one-way Binder calls.	2010-08-31 13:16:49 -07:00
IPermissionController.cpp
IServiceManager.cpp
MemoryBase.cpp
MemoryDealer.cpp
MemoryHeapBase.cpp
MemoryHeapPmem.cpp
Parcel.cpp	Don't propagate StrictMode over one-way Binder calls.	2010-08-31 13:16:49 -07:00
Permission.cpp
ProcessState.cpp
Static.cpp