d2229a65f53e7b9e9fc861ac300607a329153c4c |
|
11-Jul-2017 |
Daichi Hirono <hirono@google.com> |
Fix method sinature of FuseAppLoop JNI code The file size passed to replyLookup and replyGetAttr needed to be jlong, but they were jint before the fix. Bug: 63543158 Test: Transfer 4GB+ files through ProxyFileDescriptor Change-Id: Idaf27538e067854a25ae413651d8f83f0df3f387
/frameworks/base/core/jni/com_android_internal_os_FuseAppLoop.cpp
|
77a97cdba2903a6534fcabc1b8bc79b51aef54f5 |
|
30-Mar-2017 |
Daichi Hirono <hirono@google.com> |
Pass correct size of integer to CallVoidMethod. Previously FuseAppLoop passes int values 0 to CallVoidMethod while the argument must be jlong. Bug: 35229514 Test: StorageManagerTest#testOpenProxyFileDescriptor{,_error,_async} Change-Id: Id286d38da54b4523c63f2b380596e0de06887b3a
/frameworks/base/core/jni/com_android_internal_os_FuseAppLoop.cpp
|
4f156065c860d916b649e2b464e9405cafc732e9 |
|
08-Feb-2017 |
Daichi Hirono <hirono@google.com> |
Allow apps to process ProxyFDCallback asynchrnously. Previously callback methods of ProxyFileDescriptorCallback were invoked on a background thread prepared in the framework. So all methods were invoked and processed synchronously. This was problem because if it took time to fetch bytes of one file, operations for other files were also blocked. The CL changes ProxyFileDescriptorCallback methods to be invoked on Handler passed by apps. Now application can prepare a Handler per file so that one file does not block others. Bug: 35229514 Test: cts-tradefed run cts -m CtsOsTestCases -t android.os.storage.cts.StorageManagerTest#testOpenProxyFileDescriptor_async Change-Id: Ibadc4aad4c0373a3da586459a8f775e40288c895
/frameworks/base/core/jni/com_android_internal_os_FuseAppLoop.cpp
|
9fb00183a04036a58ee208f5bfd6c9768982f0aa |
|
08-Nov-2016 |
Daichi Hirono <hirono@google.com> |
Add StorageManager#openProxyFileDescriptor. The CL: * Adds StorageManager#openProxyFileDescriptor API. * Turns IProxyFileDescriptorCallback into a class so that it can provides default implementations. * Removes mActive state from FuseAppLoop, because the state will be managed at the MountService side. * Adds StorageManagerIntegrationTest to check if FUSE is correctly mounted or not. Since it's implementation details, CTS does not help to test the behavior. Test: StorageManagerIntegrationTest Bug: 29970149 Change-Id: Id78dd4abcf9325820e9c77c264f54bfa77b85a92
/frameworks/base/core/jni/com_android_internal_os_FuseAppLoop.cpp
|
878e86f38f87cc5dc537ffc623b04f9a779fb080 |
|
31-Oct-2016 |
Daichi Hirono <hirono@google.com> |
Adding FUSE loop thread in app side. The CL adds FuseAppLoop internal class to the framework. It parses FUSE commands from the proxy in the system service and invokes a callback provided by application. Bug: 29970149 Test: None, will be tested with CTS for StorageManager#openProxyFileDescriptor. Change-Id: I10b2add4c2743fb91eae3cb194f55843a74fb668
/frameworks/base/core/jni/com_android_internal_os_FuseAppLoop.cpp
|