No description
ca8a75680f
In Pie, Google added checks to prevent destroying of the same mutexes consecutively, and aborts the program on fortify fatal call. Our camera blobs trigger this check when tearing down an ISP session, destroying the same mutex consecutively by adding a destroy instruction in a loop. This causes the whole daemon to crash and fail. (Specifically, the violating instructions were from isp_module_stop_session and when isp_module_start_session fails to create a thread.) Workaround the issue by shimming the function; catching destroyed mutexes and returning -EBUSY without passing on the bad mutexes to libc. Change-Id: I4f8542a496dc25c53f8208a647cc0d6acc8662eb |
||
|---|---|---|
| interfaces | ||
| libbase | ||
| libbinder | ||
| libc | ||
| libcamera_metadata | ||
| libcomparetf2 | ||
| libcutils | ||
| libgui | ||
| libmemset | ||
| libpiex | ||
| libtinyxml2 | ||
| libui | ||
| libutils | ||
| .clang-format | ||
| Android.bp | ||