Victor Hsieh 58a5e9b9c0 Migrate to use fuse crate's FuseConfig API ... The old API is deprecated with a new replacement in https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3514617 Note that the original API uses write/read in an opposite perspective: a write to the filesystem by another process is a read to these FUSE filesystems. Which is also inconsistent to the mount opion of max_read. The new API brings consistency. For this specific change: - zipfuse happened to name them in the opposite (but now correct) way. - authfs happened to use the same values for both, so just update the comments. Also remove the comment in remote_file.rs that mentioned the old API. It's not super helpful anyway with the compiler check. Bug: 223659448 Test: atest AuthFsHostTest Change-Id: I33436cdc3bf84c3a0d42a6b517fe9ef28958292a		2022-04-06 17:36:02 -07:00
..
.cargo	zipfuse: supports zip on block device	2021-05-24 08:18:19 +09:00
src	Migrate to use fuse crate's FuseConfig API	2022-04-06 17:36:02 -07:00
testdata	zipfuse: add a test for deflate	2021-05-24 07:51:32 +09:00
Android.bp	Run apk mount utils from microdroid_manager	2021-12-01 19:49:41 +09:00
AndroidTest.xml	zipfuse: a read-only fuse implementation for zip archive	2021-05-12 19:47:41 +09:00
Cargo.toml	zipfuse: optimize for uncompressed zip entries	2021-08-31 08:45:07 +09:00
TEST_MAPPING	Add zipfuse to hwasan-postsubmit	2022-03-24 18:31:01 +00:00