summaryrefslogtreecommitdiff
path: root/kernel/sched/core.c
diff options
context:
space:
mode:
authorGeorg Veichtlbauer <georg@vware.at>2023-05-05 22:54:31 +0200
committerDavide Garberi <dade.garberi@gmail.com>2023-05-22 19:29:39 +0200
commit7ef1b1f38a94bf54b215c4c56ea8d62ec607f73b (patch)
tree5ccd47727a21e268b014a44ce64d575ddbc03d5f /kernel/sched/core.c
parentb4790673989b7d98dfeebf7f544104c4a0efd7b7 (diff)
Revert "kernel: Only expose su when daemon is running"lineage-19.1
This patch is no longer necessary because we no longer ship su add-ons, which is this patch initially designed for. Now it causes another issue which breaks custom root solution such as Magisk, as Magisk switches worker tmpfs dir to RO instead of RW for safety reasons and happens to satisfy MS_RDONLY check for su file, resulting in su file totally inaccessible. This reverts commit 08ff8a2e58eb226015fa68d577121137a7e0953f. Change-Id: If25a9ef7e64c79412948f4619e08faaedb18aa13
Diffstat (limited to 'kernel/sched/core.c')
-rw-r--r--kernel/sched/core.c32
1 files changed, 0 insertions, 32 deletions
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index d199741b4e7f..40a44876c74c 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -98,38 +98,6 @@
#define CREATE_TRACE_POINTS
#include <trace/events/sched.h>
-static atomic_t __su_instances;
-
-int su_instances(void)
-{
- return atomic_read(&__su_instances);
-}
-
-bool su_running(void)
-{
- return su_instances() > 0;
-}
-
-bool su_visible(void)
-{
- kuid_t uid = current_uid();
- if (su_running())
- return true;
- if (uid_eq(uid, GLOBAL_ROOT_UID) || uid_eq(uid, GLOBAL_SYSTEM_UID))
- return true;
- return false;
-}
-
-void su_exec(void)
-{
- atomic_inc(&__su_instances);
-}
-
-void su_exit(void)
-{
- atomic_dec(&__su_instances);
-}
-
ATOMIC_NOTIFIER_HEAD(load_alert_notifier_head);
DEFINE_MUTEX(sched_domains_mutex);