Android 12.0进程保活白名单功能实现

        在Android 12.0系统中,实现进程保活白名单功能是为了确保某些重要的应用程序即使进入后台也能长时间保持运行状态,不被系统自动杀死。这一功能的实现涉及多个核心类和文件,以下是具体的实现步骤和核心功能分析:  

一、实现步骤 

1.1 在IActivityManager.aidl中增加接口:

        需要在IActivityManager.aidl文件中增加与进程白名单相关的接口,例如void addWhiteListApp(String packageName)用于添加应用到白名单,void removeWhiteListApp(String packageName)用于从白名单中移除应用。

1.2 在ActivityManager.java中提供接口给应用调用:

        在ActivityManager.java文件中,需要实现上述接口,使得应用可以通过ActivityManager对象调用这些接口来操作进程白名单。

1.3 在ActivityManagerService.java中实现接口逻辑:

        在ActivityManagerService.java文件中,需要实现接口的具体逻辑,包括将应用添加到白名单或从白名单中移除,以及确保在系统杀进程时不杀死白名单中的进程。

1.4 在ActivityStackSupervisor和OomAdjuster.java中处理白名单进程:

        在ActivityStackSupervisor.java和OomAdjuster.java文件中,需要添加对白名单进程的处理逻辑。例如,在OomAdjuster.java中,可以修改进程的OOM(Out Of Memory)调整策略,以确保白名单中的进程在内存不足时不会被优先杀死。

二、涉及文件类路径

      frameworks/base/core/java/android/app/IActivityManager.aidlframeworks/base/core/java/android/app/ActivityManager.javaframeworks/base/services/core/java/com/android/server/am/ActivityManagerService.javaframeworks/base/services/core/java/com/android/server/wm/ActivityTaskSupervisor.javaframeworks/base/services/core/java/com/android/server/am/OomAdjuster.java

三、具体实现

  3.1 app进程保活白名单功能实现的核心功能实现和分析

   3.1.1在lActivityManager.aidl@中新增进程白名单的接口

       void killUidForPermissionChange(int appId, int userId, String reason);boolean enableAppFreezer(in boolean enable);+    List<String> getWhiteAppProcessList();+    void setWhiteAppProcessList(in List<String> whiteAppProcessList);

 3.1.2在ActivityManager.java中增加白名单接口给app调用

       public List<String> getWhiteAppProcessList() {try {return getService().getWhiteAppProcessList();} catch (RemoteException e) {throw e.rethrowFromSystemServer();}}public void setWhiteAppProcessList(List<String> whiteAppProcessList) {try {getService().setWhiteAppList(whiteAppProcessList);} catch (RemoteException e) {throw e.rethrowFromSystemServer();}}

在ActivityManagerjava中增加这两个关于app进程白名单的接口,通过调用ActivityManagerService.java的白名单接口来设置app进程白名单实现保活app进程。

3.2 ActivityManagerService.java中实现lActivityManager.aidl的白名单接口

  1.实现保活白名单接口public class ActivityManagerService extends IActivityManager.Stubimplements Watchdog.Monitor, BatteryStatsImpl.BatteryCallback {private List<String> mWhiteAppProcessList = new ArrayList<String>();public void setWindowManager(WindowManagerService wm) {synchronized (this) {mWindowManager = wm;mWmInternal = LocalServices.getService(WindowManagerInternal.class);mActivityTaskManager.setWindowManager(wm);}}public void setUsageStatsManager(UsageStatsManagerInternal usageStatsManager) {mUsageStatsService = usageStatsManager;mActivityTaskManager.setUsageStatsManager(usageStatsManager);}//add core startprivate List<String> mWhiteAppProcessList;@Overridepublic List<String> getWhiteAppProcessList() {return mWhiteAppProcessList;}@Overridepublic void setWhiteAppProcessList(List<String> whiteAppProcessList) {this.mWhiteAppProcessList = whiteAppProcessList;}//add core end

从AcivityManagerService中可以看出继承了IActivityManager.Stub所以说就是IActivityManager的子类所以需要实现IAcivityManager定义的保活白名单接口接下来看下关于杀进程的相关方法.

        /*** Main function for removing an existing process from the activity manager* as a result of that process going away.  Clears out all connections* to the process.*/@GuardedBy("this")final void handleAppDiedLocked(ProcessRecord app,boolean restarting, boolean allowRestart) {int pid = app.pid;boolean kept = cleanUpApplicationRecordLocked(app, restarting, allowRestart, -1,false /*replacingPid*/);if (!kept && !restarting) {removeLruProcessLocked(app);if (pid > 0) {ProcessList.remove(pid);}}if (mProfileData.getProfileProc() == app) {clearProfilerLocked();}mAtmInternal.handleAppDied(app.getWindowProcessController(), restarting, () -> {Slog.w(TAG, "Crash of app " + app.processName+ " running instrumentation " + app.getActiveInstrumentation().mClass);Bundle info = new Bundle();info.putString("shortMsg", "Process crashed.");finishInstrumentationLocked(app, Activity.RESULT_CANCELED, info);});}

从handleAppDiedLocked的注释中可以看出在ActivityManagerService.java中主要是调用handleAppDiedLocked处理杀掉进程的功能的,而在cleanUpApplicationRecordLocked中主要处理杀进程的工作接下来看cleanUpApplicationRecordLocked相关进程处理的方法。

        @GuardedBy("this")final boolean cleanUpApplicationRecordLocked(ProcessRecord app,boolean restarting, boolean allowRestart, int index, boolean replacingPid) {if (index >= 0) {removeLruProcessLocked(app);ProcessList.remove(app.pid);}mProcessesToGc.remove(app);mPendingPssProcesses.remove(app);ProcessList.abortNextPssTime(app.procStateMemTracker);// Dismiss any open dialogs.app.getDialogController().clearAllErrorDialogs();app.setCrashing(false);app.setNotResponding(false);app.resetPackageList(mProcessStats);app.unlinkDeathRecipient();app.makeInactive(mProcessStats);app.waitingToKill = null;app.forcingToImportant = null;updateProcessForegroundLocked(app, false, 0, false);app.setHasForegroundActivities(false);app.hasShownUi = false;app.treatLikeActivity = false;app.hasAboveClient = false;app.setHasClientActivities(false);mServices.killServicesLocked(app, allowRestart);boolean restart = false;// Remove published content providers.for (int i = app.pubProviders.size() - 1; i >= 0; i--) {ContentProviderRecord cpr = app.pubProviders.valueAt(i);if (cpr.proc != app) {// If the hosting process record isn't really us, bail outcontinue;}final boolean alwaysRemove = app.bad || !allowRestart;final boolean inLaunching = removeDyingProviderLocked(app, cpr, alwaysRemove);if (!alwaysRemove && inLaunching && cpr.hasConnectionOrHandle()) {// We left the provider in the launching list, need to// restart it.restart = true;}cpr.provider = null;cpr.setProcess(null);}app.pubProviders.clear();// Take care of any launching providers waiting for this process.if (cleanupAppInLaunchingProvidersLocked(app, false)) {mProcessList.noteProcessDiedLocked(app);restart = true;}// Unregister from connected content providers.if (!app.conProviders.isEmpty()) {for (int i = app.conProviders.size() - 1; i >= 0; i--) {ContentProviderConnection conn = app.conProviders.get(i);conn.provider.connections.remove(conn);stopAssociationLocked(app.uid, app.processName, conn.provider.uid,conn.provider.appInfo.longVersionCode, conn.provider.name,conn.provider.info.processName);}app.conProviders.clear();}// At this point there may be remaining entries in mLaunchingProviders// where we were the only one waiting, so they are no longer of use.// Look for these and clean up if found.// XXX Commented out for now.  Trying to figure out a way to reproduce// the actual situation to identify what is actually going on.if (false) {for (int i = mLaunchingProviders.size() - 1; i >= 0; i--) {ContentProviderRecord cpr = mLaunchingProviders.get(i);if (cpr.connections.size() <= 0 && !cpr.hasExternalProcessHandles()) {synchronized (cpr) {cpr.launchingApp = null;cpr.notifyAll();}}}}skipCurrentReceiverLocked(app);// Unregister any receivers.for (int i = app.receivers.size() - 1; i >= 0; i--) {removeReceiverLocked(app.receivers.valueAt(i));}app.receivers.clear();// If the app is undergoing backup, tell the backup manager about itfinal BackupRecord backupTarget = mBackupTargets.get(app.userId);if (backupTarget != null && app.pid == backupTarget.app.pid) {if (DEBUG_BACKUP || DEBUG_CLEANUP) Slog.d(TAG_CLEANUP, "App "+ backupTarget.appInfo + " died during backup");mHandler.post(new Runnable() {@Overridepublic void run(){try {IBackupManager bm = IBackupManager.Stub.asInterface(ServiceManager.getService(Context.BACKUP_SERVICE));bm.agentDisconnectedForUser(app.userId, app.info.packageName);} catch (RemoteException e) {// can't happen; backup manager is local}}});}for (int i = mPendingProcessChanges.size() - 1; i >= 0; i--) {ProcessChangeItem item = mPendingProcessChanges.get(i);if (app.pid > 0 && item.pid == app.pid) {mPendingProcessChanges.remove(i);mAvailProcessChanges.add(item);}}mUiHandler.obtainMessage(DISPATCH_PROCESS_DIED_UI_MSG, app.pid, app.info.uid,null).sendToTarget();// If this is a precede instance of another process instanceallowRestart = true;synchronized (app) {if (app.mSuccessor != null) {// We don't allow restart with this ProcessRecord now,// because we have created a new one already.allowRestart = false;// If it's persistent, add the successor to mPersistentStartingProcessesif (app.isPersistent() && !app.removed) {if (mPersistentStartingProcesses.indexOf(app.mSuccessor) < 0) {mPersistentStartingProcesses.add(app.mSuccessor);}}// clean up the field so the successor's proc starter could proceed.app.mSuccessor.mPrecedence = null;app.mSuccessor = null;// Notify if anyone is waiting for it.app.notifyAll();}}// If the caller is restarting this app, then leave it in its// current lists and let the caller take care of it.if (restarting) {return false;}if (!app.isPersistent() || app.isolated) {if (DEBUG_PROCESSES || DEBUG_CLEANUP) Slog.v(TAG_CLEANUP,"Removing non-persistent process during cleanup: " + app);if (!replacingPid) {mProcessList.removeProcessNameLocked(app.processName, app.uid, app);}mAtmInternal.clearHeavyWeightProcessIfEquals(app.getWindowProcessController());} else if (!app.removed) {// This app is persistent, so we need to keep its record around.// If it is not already on the pending app list, add it there// and start a new process for it.if (mPersistentStartingProcesses.indexOf(app) < 0) {mPersistentStartingProcesses.add(app);restart = true;}}.....return false;}

在cleanUpApplicationRecordLocked中的进行进程列表遍历的时候,判断app是否清除的时候根据if (!app.isPersistent() app.isolated)
调用 mAtmlntemnal.clearHeavyWeightProcesslfEquals(app.getWindowProcesscontroler();来杀掉进程所以可以在这里增加判断添加
看是否杀掉进程
具体修改如下:

    --- a/frameworks/base/services/core/java/com/android/server/am/ActivityManagerService.java+++ b/frameworks/base/services/core/java/com/android/server/am/ActivityManagerService.java@@ -14079,8 +14079,13 @@ public class ActivityManagerService extends IActivityManager.Stubif (restarting) {return false;}--        if (!app.isPersistent() || app.isolated) {+                List<String> lists=    this.mWhiteAppProcessList;+                boolean iskeepAlive=false;+                if(lists!=null && lists.contains(app.processName)){+                        iskeepAlive=true;+                }+        if ((!app.isPersistent() || app.isolated) && !iskeepAlive) {if (DEBUG_PROCESSES || DEBUG_CLEANUP) Slog.v(TAG_CLEANUP,"Removing non-persistent process during cleanup: " + app);if (!replacingPid) {@@ -14097,6 +14102,7 @@ public class ActivityManagerService extends IActivityManager.Stub// This app is persistent, so we need to keep its record around.// If it is not already on the pending app list, add it there// and start a new process for it.if (mPersistentStartingProcesses.indexOf(app) < 0) {mPersistentStartingProcesses.add(app);restart = true;

3.3 ActivityStackSupervisor.java中关于任务栈中杀进程的相关功能分析

             @Overridepublic void onRecentTaskRemoved(Task task, boolean wasTrimmed, boolean killProcess) {if (wasTrimmed) {// Task was trimmed from the recent tasks list -- remove the active task record as well// since the user won't really be able to go back to itremoveTaskById(task.mTaskId, killProcess, false /* removeFromRecents */,"recent-task-trimmed");}task.removedFromRecents();}boolean removeTaskById(int taskId, boolean killProcess, boolean removeFromRecents,String reason) {final Task task =mRootWindowContainer.anyTaskForId(taskId, MATCH_TASK_IN_STACKS_OR_RECENT_TASKS);if (task != null) {removeTask(task, killProcess, removeFromRecents, reason);return true;}Slog.w(TAG, "Request to remove task ignored for non-existent task " + taskId);return false;}void removeTask(Task task, boolean killProcess, boolean removeFromRecents, String reason) {if (task.mInRemoveTask) {// Prevent recursion.return;}task.mInRemoveTask = true;try {task.performClearTask(reason);cleanUpRemovedTaskLocked(task, killProcess, removeFromRecents);mService.getLockTaskController().clearLockedTask(task);mService.getTaskChangeNotificationController().notifyTaskStackChanged();if (task.isPersistable) {mService.notifyTaskPersisterLocked(null, true);}} finally {task.mInRemoveTask = false;}}

在AcivitvStackSupervisor.java中,关于移除栈内的app进程,主要是在onRecentTaskRemoved中通过调用removeTaskByld实现的,而removeTaskByld又是调用removeTask实现的,具体是在removeTask中处理的杀进程所以具体实现如下:

          boolean removeTaskById(int taskId, boolean killProcess, boolean removeFromRecents,String reason) {final Task task =mRootWindowContainer.anyTaskForId(taskId, MATCH_TASK_IN_STACKS_OR_RECENT_TASKS);if (task != null) {//add code startComponentName component = tr.getBaseIntent().getComponent();if(component!=null){String pkg=component.getPackageName();ActivityManager am = (ActivityManager) mService.mContext.getSystemService(Context.ACTIVITY_SERVICE);List<String> list=am.getWhiteAppProcessList();if(list!=null && list.contains(pkg)){return false;}}//add code endremoveTask(task, killProcess, removeFromRecents, reason);return true;}Slog.w(TAG, "Request to remove task ignored for non-existent task " + taskId);return false;}

3.4OomAdjuster.java中关于对保活白名单的分析

   +    private boolean isInWhitelist(ProcessRecord pr) {+        String pkgName = pr.info.packageName;+               List<String> mLmKillerBypassPackages = mService.getKeepAliveList();+               if(mLmKillerBypassPackages!=null && mLmKillerBypassPackages.size()>0){+                       for (String token : mLmKillerBypassPackages) {+                               if (pkgName.startsWith(token)) {+                                       return true;+                               }+                       }+               }+        return false;+    }/** Applies the computed oomadj, procstate and sched group values and freezes them in set* */@GuardedBy("mService")private final boolean applyOomAdjLocked(ProcessRecord app, boolean doingAll, long now,long nowElapsed) {boolean success = true;if (app.getCurRawAdj() != app.setRawAdj) {app.setRawAdj = app.getCurRawAdj();}int changes = 0;// don't compact during bootupif (mCachedAppOptimizer.useCompaction() && mService.mBooted) {// Cached and prev/home compactionif (app.curAdj != app.setAdj) {// Perform a minor compaction when a perceptible app becomes the prev/home app// Perform a major compaction when any app enters cached// reminder: here, setAdj is previous state, curAdj is upcoming stateif (app.setAdj <= ProcessList.PERCEPTIBLE_APP_ADJ &&(app.curAdj == ProcessList.PREVIOUS_APP_ADJ ||app.curAdj == ProcessList.HOME_APP_ADJ)) {mCachedAppOptimizer.compactAppSome(app);} else if ((app.setAdj < ProcessList.CACHED_APP_MIN_ADJ|| app.setAdj > ProcessList.CACHED_APP_MAX_ADJ)&& app.curAdj >= ProcessList.CACHED_APP_MIN_ADJ&& app.curAdj <= ProcessList.CACHED_APP_MAX_ADJ) {mCachedAppOptimizer.compactAppFull(app);}} else if (mService.mWakefulness != PowerManagerInternal.WAKEFULNESS_AWAKE&& app.setAdj < ProcessList.FOREGROUND_APP_ADJ// Because these can fire independent of oom_adj/procstate changes, we need// to throttle the actual dispatch of these requests in addition to the// processing of the requests. As a result, there is throttling both here// and in CachedAppOptimizer.&& mCachedAppOptimizer.shouldCompactPersistent(app, now)) {mCachedAppOptimizer.compactAppPersistent(app);} else if (mService.mWakefulness != PowerManagerInternal.WAKEFULNESS_AWAKE&& app.getCurProcState()== ActivityManager.PROCESS_STATE_BOUND_FOREGROUND_SERVICE&& mCachedAppOptimizer.shouldCompactBFGS(app, now)) {mCachedAppOptimizer.compactAppBfgs(app);}}if (app.curAdj != app.setAdj) {// 主要修改部分开始// 注释代码开始/*ProcessList.setOomAdj(app.pid, app.uid, app.curAdj);if (DEBUG_SWITCH || DEBUG_OOM_ADJ || mService.mCurOomAdjUid == app.info.uid) {String msg = "Set " + app.pid + " " + app.processName + " adj "+ app.curAdj + ": " + app.adjType;reportOomAdjMessageLocked(TAG_OOM_ADJ, msg);}app.setAdj = app.curAdj;app.verifiedAdj = ProcessList.INVALID_ADJ;*/// 注释代码结束+            boolean isAppWhiteProcess = false;+            if(isInWhitelist(app) && (app.curAdj > ProcessList.PERSISTENT_SERVICE_ADJ))isAppWhiteProcess = true;+            if(isAppWhiteProcess){+                Slog.d(TAG,"isAppWhiteProcess");+                ProcessList.setOomAdj(app.pid, app.uid, ProcessList.PERSISTENT_SERVICE_ADJ);+                if (DEBUG_SWITCH || DEBUG_OOM_ADJ || mService.mCurOomAdjUid == app.info.uid) {+                    String msg = "Set " + app.pid + " " + app.processName + " adj "+                            + app.curAdj + ": " + app.adjType;+                    reportOomAdjMessageLocked(TAG_OOM_ADJ, msg);+                }+                app.setAdj = ProcessList.PERSISTENT_SERVICE_ADJ;+                app.verifiedAdj = ProcessList.INVALID_ADJ;+            }else{+                ProcessList.setOomAdj(app.pid, app.uid, app.curAdj);+                if (DEBUG_SWITCH || DEBUG_OOM_ADJ || mService.mCurOomAdjUid == app.info.uid) {+                    String msg = "Set " + app.pid + " " + app.processName + " adj "+                            + app.curAdj + ": " + app.adjType;+                    reportOomAdjMessageLocked(TAG_OOM_ADJ, msg);+                }+                app.setAdj = app.curAdj;+                app.verifiedAdj = ProcessList.INVALID_ADJ;+            }}.....return success;}

在上述的OomAdjuster.java的代码中,首选通过isInWhitelist(ProcessRecord pr)判断当前进程是否在白名单之内,然后通过设置app.setAdj和app.verifiedAdj 两个值来确保app不会被杀掉.

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.mzph.cn/diannao/58026.shtml

如若内容造成侵权/违法违规/事实不符,请联系多彩编程网进行投诉反馈email:809451989@qq.com,一经查实,立即删除!

相关文章

PG数据库之索引详解

PostgreSQL数据库中的索引是一种用于提高查询性能的重要数据结构。通过索引&#xff0c;数据库可以快速定位到表中的特定行&#xff0c;而无需进行全表扫描。PostgreSQL支持多种索引类型&#xff0c;每种类型都有其特定的应用场景和性能特点。下面将详细介绍PostgreSQL中的索引…

go 使用fyne实现桌面程序的计算器例子

使用Fyne工具包构建跨平台应用是非常简单的&#xff0c;在此之前我们需要做一些准备功能做&#xff0c;比如安装一些gcc基础图形依赖库&#xff0c;还有go语言本身的运行开发环境都是必要的。 在此之前我们希望你是go语言的已入门用户&#xff0c;掌握go的协程&#xff0c;管道…

鲁班猫的一些踩坑

有坑的地方 1、安装relasense&#xff1a; 错误&#xff1a;不要采用下面的二进制安装&#xff08;在主机、Jetson可以使用&#xff09;&#xff0c;尽管也能安装并运行realsense-viwer&#xff0c;但是链接不到相机设备&#xff01; sudo apt-key adv --keyserver keyserver…

Linux基础知识 - C(自学使用)

1.C语言基础知识 参考博客&#xff1a; https://blog.csdn.net/qq_45254369/article/details/126023482?ops_request_misc%257B%2522request%255Fid%2522%253A%252277629891-A0F3-4EFC-B1AC-410093596085%2522%252C%2522scm%2522%253A%252220140713.130102334.pc%255Fblog.%…

Xcode文件默认存储位置-使用c++file保存文件默认路径以及设置为路径为当前项目路径

Xcode文件默认存储位置-使用cfile保存文件默认路径以及设置为路径为当前项目路径 1.概述 使用Xcode工具开发时候&#xff0c;遇到C调用file创建文件后&#xff0c;在当前项目中找不到文件路径。这是由于xcode会将文件保存到默认设置的路径。下面是查看文件默认存储路径和修改…

DC-9靶场渗透

靶机&#xff1a;DC-9 DC: 9 ~ VulnHub 攻击机&#xff1a;kail linux 2024 1,将两台虚拟机网络连接都改为NAT模式&#xff0c;并查看DC-9的MAC地址 2&#xff0c;进行主机扫描&#xff0c;通过MAC地址发现靶机的IP地址 攻击机IP地址192.168.23.169&#xff0c;靶机IP地址192.1…

MySQL-存储过程/函数/触发器

文章目录 什么是存储过程存储过程的优缺点存储过程的基本使用存储过程的创建存储过程的调用存储过程的删除存储过程的查看delimiter命令 MySQL中的变量系统变量用户变量局部变量参数 if语句case语句while循环repeat循环loop循环游标cursor捕获异常并处理存储函数触发器触发器概…

QT QGestureEvent支持平移,缩放,旋转触摸板手势

一.Gesture释义 平移:点按住触控板,然后拖移,实现平移功能。 缩放:在触控板上,双指张开实现放大,双指合拢实现缩小。 旋转:在触控板上,双指分别反方向移动旋转,实现旋转功能。 二.实现功能 1.重写bool event(QEvent *event) override事件: bool ImageWidget::event…

16. 虚拟化

文章目录 第16章 虚拟化16.1 共享资源16.2 虚拟机16.3 虚拟机镜像16.4 容器16.5 容器和虚拟机16.6 容器的可移植性16.7 Pod&#xff08;容器组&#xff09;16.8 无服务器架构16.9 小结16.10 扩展阅读16.11 问题讨论 第16章 虚拟化 “虚拟”意味着永远不知道你的下一个字节从哪里…

SpringBoot poi-tl通过模板占位符生成word文件

简介&#xff1a; 开发中我们需要通过在word中使用占位符来动态渲染一些数据&#xff0c;本文讲解poi-tl实现动态生成word文档&#xff0c;包括表格循环&#xff0c;对象嵌套。 poi-tl官网文档 Poi-tl Documentation 1. word格式 这是我的test.word 这是导出后的out.docx文件 …

蓝桥杯普及题

[蓝桥杯 2024 省 B] 好数 题目描述 一个整数如果按从低位到高位的顺序,奇数位(个位、百位、万位……)上的数字是奇数,偶数位(十位、千位、十万位……)上的数字是偶数,我们就称之为“好数”。 给定一个正整数 N N N,请计算从 1 1

UE4 材质学习笔记12(水体反射和折射)

一.水体反射和折射 首先就是要断开所有连接到根节点的线&#xff0c;因为水有很多不同的节点成分&#xff0c;当所有其他节点都在用时 要分辨出其中一个是何效果是很难的。 虚幻有五种不同的方法可以创建反射&#xff0c;虚幻中的大多数场景使用多种这些方法 它们会同时运作。…

opencv-platform实现人脸识别

和同事接触了下甲方,对方算是一个资源整合的自由人&#xff0c;手里有项目&#xff0c;然后认识些开发就聊下有什么事情可以做的&#xff0c;对方聊了下做人脸签到&#xff0c;或者说人脸打开。就这方面我做了下简单的了解。做了个java小demo。 我们常用的人脸识别的摄像头屏幕…

shell脚本语言-需要算法?

文章目录 1. 冒泡排序2. 搜索算法3. 文本处理4. 文件操作5. 条件语句6. 循环 Shell脚本语言本身并不包含高级编程语言中的“算法”概念&#xff0c;如排序算法或搜索算法。Shell脚本主要用于自动化命令行任务&#xff0c;如文件操作、文本处理、程序执行等。不过&#xff0c;Sh…

ctfshow-文件上传-151-161

CTFshow文件上传 PHP文件上传&#xff1a;1、代码思路 黑名单是设置不能通过的用户&#xff0c;黑名单以外的用户都能通过。 phtml、pht、php3、php4、php5后缀都会按做php文件执行&#xff0c;且不在黑名单内。 2、绕过 找漏网之鱼:cer、php3、php4、phtml等。 大小写绕…

使用SpringBoot自定义注解+AOP+redisson锁来实现防接口幂等性重复提交

1 前提&#xff0c;整合好springboot和redis,redisson的环境 <dependency><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter-aop</artifactId> </dependency> 2 编写自定义注解&#xff0c;注解的作用是标记…

反编译华为-研究功耗联网监控日志

摘要 待机功耗中联网目前已知的盲点&#xff1a;App自己都不知道的push类型的被动联网、app下载场景所需时长、组播联网、路由器打醒AP。 竞品 策略 华为 灭屏使用handler定时检测&#xff08;若灭屏30分钟内则周期1分钟&#xff0c;否则为2分钟&#xff09;&#xff0c;检…

第13次CCF CSP认证真题解

1、跳一跳 题目链接&#xff1a;https://sim.csp.thusaac.com/contest/13/problem/0 本题是小游戏“跳一跳”的模拟题&#xff0c;按照题意模拟即可。 100分代码&#xff1a; #include <iostream> using namespace std; int main(int argc, char *argv[]) {int n 30…

中国人寿财险青岛市分公司:科技保险,助力企业高质量发展

中国人寿财险青岛市分公司深知科技保险对于企业发展的重要性&#xff0c;积极将科技保险融入企业发展战略。公司利用科技手段&#xff0c;为企业提供风险评估、防灾减灾等增值服务&#xff0c;帮助企业降低经营风险。同时&#xff0c;公司还通过科技保险产品&#xff0c;为企业…

第十七周:机器学习

目录 摘要 Abstract 一、MCMC 1、马尔科夫链采样 step1 状态设定 step2 转移矩阵 step3 马尔科夫链的生成 step4 概率分布的估计 2、蒙特卡洛方法 step1 由一个分布产生随机变量 step2 用这些随机变量做实验 3、MCMC算法 4、参考文章 二、flow-based GAN 1、引…