From a3209c5f5784b1d8442c9b6f8d852e1764917854 Mon Sep 17 00:00:00 2001
From: Zim <zezeozue@google.com>
Date: Tue, 11 Feb 2020 16:55:06 +0000
Subject: [PATCH] Explicitly disable FUSE

It is already disabled, but having an explcit value in the prop makes
some code in the system_server, easier.

Will follow up with a cl to explicitly enable it on internal master,
aosp will remain this way since it doesn't have the additional
components to run FUSE.

Test: Freshly wiped and flashed device has persist.sys.fuse set to false
Bug: 135341433
Merged-In: I1493e2806823b5751794a9a17ee248dc72b857ff
Change-Id: Ibb955a543e367aa2f4518d5c1c4d070cd084eca0
---
 rootdir/init.rc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/rootdir/init.rc b/rootdir/init.rc
index 5f4b8c3ab..c769f79cb 100644
--- a/rootdir/init.rc
+++ b/rootdir/init.rc
@@ -739,6 +739,9 @@ on post-fs-data
     # IOCTLs on ashmem fds any more.
     setprop sys.use_memfd false
 
+    # Explicitly disable FUSE
+    setprop persist.sys.fuse false
+
     # Set fscklog permission
     chown root system /dev/fscklogs/log
     chmod 0770 /dev/fscklogs/log