Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Short term fix: Allow native processes for Logcat data access

Browse Source 
We allow native processes as a short term solution.

Bug: 218293986
Test: CtsVerifier
Ignore-AOSP-First: pending fix for logcat privacy issue
Change-Id: Ib73305700349f98035a689ffcb4b1fa9e8728eb3
This commit is contained in:
eunjeongshin
2022-02-07 19:55:27 +00:00
parent 128ef9317f
commit b19cc07516
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
services/core/java/com/android/server/logcat/LogcatManagerService.java
View File

@@ -59,7 +59,7 @@ public final class LogcatManagerService extends SystemService {
private ActivityManagerInternal mActivityManagerInternal;
private static final int MAX_UID_IMPORTANCE_COUNT_LISTENER = 2;
private static int sUidImportanceListenerCount = 0;
private static final int AID_SHELL_UID = 2000;
private static final int AID_APP_UID = 10000;
// TODO This allowlist is just a temporary workaround for the tests:
// FrameworksServicesTests
@@ -339,8 +339,10 @@ public final class LogcatManagerService extends SystemService {
return;
}
// If the access request is coming from adb shell, approve the logd access
if (mUid == AID_SHELL_UID) {
// If the access request is coming from native apps, approve the logd access
// TODO: This is needed to make tooling to work. However,
// we intend to be stricter with respect to native processes in a follow-up CL
if (mUid < AID_APP_UID) {
try {
getLogdService().approve(mUid, mGid, mPid, mFd);
} catch (RemoteException e) {