platform_system_core/libappfuse
hyeeun.jun@samsung.com 49545ab897 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

Bug : https://issuetracker.google.com/issues/145707568
Signed-off-by: hyeeun.jun@samsung.com <hyeeun.jun@samsung.com>

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.
2020-02-18 04:33:06 +00:00
..
include/libappfuse Fix Deadlock Issue On AppFuseBridge 2020-02-18 04:33:06 +00:00
tests Skip FUSE request from /dev/fuse if unique=0 2017-06-20 00:25:28 +00:00
Android.bp bpfmt. 2018-02-16 17:58:14 -08:00
AndroidTest.xml Add test config to libappfuse_test 2017-03-31 17:11:50 -07:00
EpollController.cc Add new EpollController class. 2017-03-15 15:58:06 +09:00
FuseAppLoop.cc Change FuseAppLoop so that it can process messages asynchronously. 2017-03-29 00:13:58 +00:00
FuseBridgeLoop.cc Fix Deadlock Issue On AppFuseBridge 2020-02-18 04:33:06 +00:00
FuseBuffer.cc Stop using SO_SNDBUFFORCE 2018-03-15 14:22:27 +09:00
OWNERS Add OWNERS. 2017-12-07 13:30:03 -08:00