diff options
| author | hyeeun.jun@samsung.com <hyeeun.jun@samsung.com> | 2020-01-29 17:09:06 +0900 |
|---|---|---|
| committer | Narayan Kamath <narayan@google.com> | 2020-06-17 13:45:13 +0100 |
| commit | f8a1cec8d5d054e16bf2788f3a3f1a06dd20ec4d (patch) | |
| tree | fa972fc1ff1cbc30e77997419c3cb74f710e6dc9 /tools/aapt2/java/JavaClassGenerator.cpp | |
| parent | e6c5d04a218d3fd2dffce71058254798f509bbce (diff) | |
Fix Deadlock Issue On AppFuseBridge
There are two locks used by AppFuseBridge.
First is it's object lock, and the second is a mutex lock in app fuse library.
There are two oppsite routines to get those locks.
(Thread A) Got Java lock -> Try to get Native lock
(Thread B) Got Native lock -> Try to get Java lock
The order must be followed to obtain two locks.
If not, the dead lock will be caused.
Therefore we change the routine to get the mutex lock first, and the object lock later.
Signed-off-by: hyeeun.jun@samsung.com <hyeeun.jun@samsung.com>
Bug: https://issuetracker.google.com/issues/145707568
Bug: 157535024
Test: atest --test-mapping apex/blobstore
Change-Id: I1f05cc98953d8452147370dd04c223d54c0e5362
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions