5048b4b2bc
Mounting a FUSE path needs two steps: 1. Mounting the filesystem 2. Starting the FUSE session in the FUSE daemon The second part requires retriving an fd from (1) and the mount paths and passing it to the FUSE daemon. Previously, we'd return from the Vold mount call and mark the volume as mounted while we scramble to do (2). This means there's a time period where the Volume is marked as MOUNTED but not actually ready and any IO access on the paths will hang forever. This could also be misleading when interpreting bug reports. Now, we block the Vold mount call until the FUSE session is started Test: atest AdoptableHostTest Bug: 144275217 Change-Id: I45238a31df71286f67ef1c65c711d0085d72e97f
23 lines
807 B
Text
23 lines
807 B
Text
/*
|
|
* Copyright (C) 2019 The Android Open Source Project
|
|
*
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
* you may not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*/
|
|
|
|
package android.os;
|
|
|
|
/** {@hide} */
|
|
interface IVoldMountCallback {
|
|
boolean onVolumeChecking(FileDescriptor fuseFd, @utf8InCpp String path,
|
|
@utf8InCpp String internalPath);
|
|
}
|