topjohnwu ada0f93686 Apply all sepolicy patches pre-init ... Boot services tend to fail in the middle when the kernel loads a sepolicy live. It seems that moving full patch (allow magisk * * *) to late_start is still not enough to fix service startup failures. So screw it, apply all patched in magiskinit, which makes sure that all rules are only loaded in a single step. The only down side is that some OEM with a HUGE set of secontexts (e.g. Samsung) might suffer a slightly longer boot time, which IS the reason why the rules are split to 2 parts in the first place.		2018-08-09 03:20:28 +08:00
..
bootstages.c	Apply all sepolicy patches pre-init	2018-08-09 03:20:28 +08:00
daemon.c	Apply all sepolicy patches pre-init	2018-08-09 03:20:28 +08:00
db.c	Install stub APK when needed	2018-06-14 05:09:54 +08:00
log_daemon.c	Try logging a little harder	2018-08-03 01:58:56 +08:00
magisk.c	Separate logging into its own daemon	2018-07-02 22:11:28 +08:00
magiskinit.c	Apply all sepolicy patches pre-init	2018-08-09 03:20:28 +08:00
socket.c	Separate logging into its own daemon	2018-07-02 22:11:28 +08:00