From f59c55aa7a40085d5df1e2b17719f8e23a433316 Mon Sep 17 00:00:00 2001
From: Steve Muckle <smuckle@google.com>
Date: Wed, 10 May 2017 13:24:31 -0700
Subject: [PATCH] Revert "disable module loading after BOOT_COMPLETED
 broadcast"

This reverts commit 6ed19d1675ab7a9b45d1b82c90aac2be8f408a2e.

Allow devices to decide for themselves whether to allow
module loading after boot.

Bug: 38204366
Test: boot sailfish, load a kernel module
Change-Id: Ib9e77381de9003fb5160463664015a95316ddfc5
---
 rootdir/init.rc | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/rootdir/init.rc b/rootdir/init.rc
index def686bc0..944aae708 100644
--- a/rootdir/init.rc
+++ b/rootdir/init.rc
@@ -657,12 +657,6 @@ on property:vold.decrypt=trigger_shutdown_framework
 on property:sys.boot_completed=1
     bootchart stop
 
-on property:sys.boot_completed=1 && property:ro.build.type=user
-    write /proc/sys/kernel/modules_disabled 1
-
-on property:sys.boot_completed=1 && property:ro.build.type=userdebug
-    write /proc/sys/kernel/modules_disabled 1
-
 # system server cannot write to /proc/sys files,
 # and chown/chmod does not work for /proc/sys/ entries.
 # So proxy writes through init.