CTS问题分析一

最新推荐文章于 2024-09-18 17:21:54 发布
最新推荐文章于 2024-09-18 17:21:54 发布
阅读量3.1k 收藏
点赞数
分类专栏： CTS
原文链接：https://www.jianshu.com/p/841638c5ca0a
版权

CTS/GTS问题分析一

android.security.cts.ListeningPortsTest#testNoListeningLoopbackTcp6Ports
android.security.cts.ListeningPortsTest#testNoListeningLoopbackUdp6Ports
android.security.cts.ListeningPortsTest#testNoRemotelyAccessibleListeningUdp6Ports

问题分析

本地测了一下，前两条没问题，那么下面重点先说下第三条的分析流程:

测试命令: run sts-userbuild -m CtsSecurityTestCases -t android.security.cts.ListeningPortsTest#testNoRemotelyAccessibleListeningUdp6Ports

测试结果:

Found port listening on addr=fe80::77b0:8288:f0d8:d4c6, port=40066, UID=1000 [com.miui.screenrecorder, com.qti.service.colorservice, com.qualcomm.atfwd, com.goodix.fingerprint, com.android.wallpaperbackup, com.xiaomi.powerchecker, com.qualcomm.qti.seemp.service, com.qualcomm.qti.smcinvokepkgmgr, com.miui.contentcatcher, com.qualcomm.qti.services.secureui, com.miui.securitycore, com.wapi.wapicertmanage, com.qualcomm.qti.qtisystemservice, com.xiaomi.mbnloader, com.dsi.ant.server, com.xiaomi.location.fused, com.qti.diagservices, com.qualcomm.qti.usta, com.fingerprints.extension.service, com.miui.cleanmaster, com.miui.daemon, com.android.settings, com.android.systemui, com.qti.dpmserviceapp, com.miui.freeform, com.qualcomm.wfd.service, com.xiaomi.bttester, com.quicinc.cne.CNEService, com.miui.powerkeeper, com.qualcomm.location, com.qualcomm.qti.poweroffalarm, com.miui.cloudservice.sysbase, com.qualcomm.qti.callenhancement, com.miui.cit, com.qualcomm.qti.qmmi, org.codeaurora.gps.gpslogsave, com.miui.system, com.miui.touchassistant, com.miui.klo.bugreport, com.android.inputdevices, com.android.providers.settings, com.miui.securitycenter, org.codeaurora.btmultisim, com.xiaomi.joyose, com.qualcomm.qti.seccamservice, com.miui.antispam, com.qualcomm.svi, com.qualcomm.cabl, com.miui.rom, com.miui.bugreport, android, org.simalliance.openmobileapi.service, com.qualcomm.qti.uceShimService, com.android.keychain, com.miui.sysopt, com.miui.wmsvc, com.android.server.telecom, com.miui.qr, com.qti.csm, com.android.provision, com.qualcomm.qti.sensors.qsensortest, com.xiaomi.drivemode, com.android.location.fused] in /proc/net/udp6
Found port listening on addr=fe80::77b0:8288:f0d8:d4c6, port=49636, UID=1000 [com.miui.screenrecorder, com.qti.service.colorservice, com.qualcomm.atfwd, com.goodix.fingerprint, com.android.wallpaperbackup, com.xiaomi.powerchecker, com.qualcomm.qti.seemp.service, com.qualcomm.qti.smcinvokepkgmgr, com.miui.contentcatcher, com.qualcomm.qti.services.secureui, com.miui.securitycore, com.wapi.wapicertmanage, com.qualcomm.qti.qtisystemservice, com.xiaomi.mbnloader, com.dsi.ant.server, com.xiaomi.location.fused, com.qti.diagservices, com.qualcomm.qti.usta, com.fingerprints.extension.service, com.miui.cleanmaster, com.miui.daemon, com.android.settings, com.android.systemui, com.qti.dpmserviceapp, com.miui.freeform, com.qualcomm.wfd.service, com.xiaomi.bttester, com.quicinc.cne.CNEService, com.miui.powerkeeper, com.qualcomm.location, com.qualcomm.qti.poweroffalarm, com.miui.cloudservice.sysbase, com.qualcomm.qti.callenhancement, com.miui.cit, com.qualcomm.qti.qmmi, org.codeaurora.gps.gpslogsave, com.miui.system, com.miui.touchassistant, com.miui.klo.bugreport, com.android.inputdevices, com.android.providers.settings, com.miui.securitycenter, org.codeaurora.btmultisim, com.xiaomi.joyose, com.qualcomm.qti.seccamservice, com.miui.antispam, com.qualcomm.svi, com.qualcomm.cabl, com.miui.rom, com.miui.bugreport, android, org.simalliance.openmobileapi.service, com.qualcomm.qti.uceShimService, com.android.keychain, com.miui.sysopt, com.miui.wmsvc, com.android.server.telecom, com.miui.qr, com.qti.csm, com.android.provision, com.qualcomm.qti.sensors.qsensortest, com.xiaomi.drivemode, com.android.location.fused] in /proc/net/udp6

因为报错的uid = 1000,所以共享这个uid的进程都会被打出来，影响真正的判断，因此需要通过下面的步骤找出真正的fail项:

      1. adb shell
      2. su
      3. polaris:/ # cat /proc/net/udp6 
sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops
149: 00000000000000000000000000000000:A9CE 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38655 2 0000000000000000 0
841: 000080FE000000008882B077C6D4D8F0:9C82 00000000000000000000000000000000:0000 07 00000000:00000000 00:00000000 00000000 1000 0 35682 2 0000000000000000 0
926: 00000000000000000000000000000000:9CD7 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38659 2 0000000000000000 0
934: 00000000000000000000000000000000:9CDF 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38671 2 0000000000000000 0
1193: 00000000000000000000000000000000:9DE2 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38675 2 0000000000000000 0
2208: 00000000000000000000000000000000:A1D9 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38667 2 0000000000000000 0
2219: 000080FE000000008882B077C6D4D8F0:C1E4 00000000000000000000000000000000:0000 07 00000000:00000000 00:00000000 00000000 1000 0 35680 2 0000000000000000 0
2507: 00000000000000000000000000000000:A304 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38647 2 0000000000000000 0
2595: 00000000000000000000000000000000:C35C 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 37765 2 0000000000000000 0
2596: 00000000000000000000000000000000:C35D 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 37766 2 0000000000000000 0
2597: 00000000000000000000000000000000:C35E 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 37755 2 0000000000000000 0
2598: 00000000000000000000000000000000:C35F 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 37756 2 0000000000000000 0
2603: 00000000000000000000000000000000:C364 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38722 2 0000000000000000 0
2604: 00000000000000000000000000000000:C365 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38723 2 0000000000000000 0
2607: 00000000000000000000000000000000:C368 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38738 2 0000000000000000 0
2608: 00000000000000000000000000000000:C369 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38739 2 0000000000000000 0
2611: 00000000000000000000000000000000:C36C 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38758 2 0000000000000000 0
2612: 00000000000000000000000000000000:C36D 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38759 2 0000000000000000 0
2617: 00000000000000000000000000000000:C372 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 37747 2 0000000000000000 0
2618: 00000000000000000000000000000000:C373 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 37748 2 0000000000000000 0
2619: 00000000000000000000000000000000:C374 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38730 2 0000000000000000 0
2620: 00000000000000000000000000000000:C375 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38731 2 0000000000000000 0
2623: 00000000000000000000000000000000:C378 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38706 2 0000000000000000 0
2624: 00000000000000000000000000000000:C379 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38707 2 0000000000000000 0
2628: 00000000000000000000000000000000:A37D 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38683 2 0000000000000000 0
2629: 00000000000000000000000000000000:C37E 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38698 2 0000000000000000 0
2630: 00000000000000000000000000000000:C37F 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38699 2 0000000000000000 0
2639: 00000000000000000000000000000000:C388 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38768 2 0000000000000000 0
2640: 00000000000000000000000000000000:C389 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38769 2 0000000000000000 0
2641: 00000000000000000000000000000000:C38A 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38746 2 0000000000000000 0
2642: 00000000000000000000000000000000:C38B 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38747 2 0000000000000000 0
2643: 00000000000000000000000000000000:C38C 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38714 2 0000000000000000 0
2644: 00000000000000000000000000000000:C38D 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38715 2 0000000000000000 0
2783: 00000000000000000000000000000000:A418 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38691 2 0000000000000000 0
2925: 00000000000000000000000000000000:A4A6 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38687 2 0000000000000000 0
3446: 00000000000000000000000000000000:A6AF 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38663 2 0000000000000000 0
3497: 00000000000000000000000000000000:A6E2 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38679 2 0000000000000000 0
3771: 00000000000000000000000000000000:A7F4 00000000000000000000000000000000:0000 87 00000000:00000000 00:00000000 00000000 1001 0 38651 2 0000000000000000 0

找到uid=1000的行，找出其中的inode值，此处为35682

       4. polaris:/ # ls -l /proc/*/fd | grep 35682

lrwx------ 1 root root 64 2018-08-13 12:20 26 -> socket:[35682]     

       5. polaris:/ # ls -l /proc/*/fd/26

l-wx------ 1 root root 64 2018-08-13 12:32 /proc/1018/fd/26 -> /dev/pmsg0
l-wx------ 1 gps gps 64 2018-08-13 12:20 /proc/1023/fd/26 -> pipe:[36017]
lrwx------ 1 root root 64 2018-08-13 12:20 /proc/1182/fd/26 -> socket:[29611]
lrwx------ 1 radio radio 64 2018-08-13 12:20 /proc/1207/fd/26 -> socket:[37162]
lrwx------ 1 root root 64 2018-08-13 12:32 /proc/1222/fd/26 -> socket:[42078]
lr-x------ 1 root root 64 2018-08-13 12:20 /proc/1224/fd/26 -> pipe:[33964]
lr-x------ 1 system system 64 2018-08-13 12:32 /proc/1397/fd/26 -> /system/framework/android.hidl.manager-V1.0-java.jar
lrwx------ 1 root root 64 2018-08-13 12:20 /proc/1725/fd/26 -> socket:[35682]
lr-x------ 1 system system 64 2018-08-13 12:32 /proc/1947/fd/26 -> /system/framework/android.hidl.manager-V1.0-java.jar
lr-x------ 1 root root 64 2018-08-13 12:20 /proc/1993/fd/26 -> /system/framework/android.hidl.manager-V1.0-java.jar
lr-x------ 1 u0_a76 u0_a76 64 2018-08-13 12:32 /proc/2013/fd/26 -> /system/framework/android.hidl.manager-V1.0-java.jar

       6. polaris:/ # ps -A | grep 1725

system        1725     1   47296  11704 binder_thread_read  0 S ims_rtp_daemo

则找到影响的对应进程

问题总结

这个问题如果直接报出其他进程，其实非常好处理；但是报出uid=1000的项，就需要按照上面的步骤确认下再进行处理，后续考虑写成脚本处理


 

快導碗里来
关注
专栏目录
CtsDeqpTestCases fail
Judy889的专栏
07-27 4323
Suite / Plan:VTS / cts-on-gsi Suite / Build: 8.1_R4 / 4766758 test_result_failures.html显示： dEQP-GLES3.functional.shaders.declarations.invalid_declarations#uniform_block_in_vertex fail === with ...
Android CTS（兼容性测试）
我的博客
05-27 5607
Android CTS测试 一、Android CTS测试简介 CTS全称Compatibility Test Suite兼容性测试工具，为了保证开发的应用在所有兼容Android的设备上正常运行，并保证一致的用户体验，Google制定了CTS来确保设备运行的Android系统全面兼容Android规范，Google也提供了一份兼容性标准文档（Compatibility Definition
【自用，仅供参考】小米澎湃1.0.6.0 ADB可卸载2024.9.18备份
最新发布
member1113的专栏
09-18 3543
可卸载名单：com.miui.miwallpaper.overlay.customize（wallpaper系列--不止这一个--是壁纸相关程序，本人不用，要用的请误删除，其他请自测或根据后面内容自己查询）
CTS典型问题分析处理
AndyTsui的专栏
03-14 5844
<br />(1) android.net.cts.ListeningPortsTest#testNoListeningPorts<br />cts_host > start --plan Android -t android.net.cts.ListeningPortsTest#testNoListeningPorts<br />start test android.net.cts.ListeningPortsTest#testNoListeningPorts<br />=================
[Android GMS 认证] CTS 问题列表之 CtsSecurityTestCases
zhms的专栏
10-27 1382
run cts -m CtsSecurityTestCases -t android.security.cts.StagefrightTest#testStagefright_cve_2015_6600 --skip-preconditions  这是高通闭源部分的问题，向高通要patch。 LINUX/android/vendor/qcom/proprietary/prebuilt_HY11...
Cts 失败项之CtsAppSecurityHostTestCases
jeephao的博客
09-23 2464
Cts 失败项之CtsAppSecurityHostTestCases
CtsAppSecurityHostTestCases--android.appsecurity.cts.DirectBootHostTest#testDirectBootEmulated
fan380485838的专栏
01-16 1870
platform/frameworks/base / cmds/sm/src/com/android/commands/sm/Sm.java   public void runSetEmulateFbe() throws RemoteException {          //james.fan 2017-01-17,solve cts testDirectBootEmulated fail...
CTS-DEBUG CtsAppSecurityHostTestCases AdoptableHostTest#testApps
yxdspirit的专栏
08-25 1561
# CTS-DEBUG CtsAppSecurityHostTestCases AdoptableHostTest#testApps 这个case 其实是和testEjected 是一样的，如果出现了和我上一篇一样的问题（Expected private volume; found [private:179,66 unmountable 02f80bf6-ac2d-4afa-99be-6869b479334c, private mounted null]），可以参考上一篇解决方案。这个其实是一整块的ca.
android cts问题分析,CTS问题分析6
weixin_30315143的博客
05-25 1481
CTS/GTS问题分析6遇到一个Android P相关的问题，和原来CTS/GTS 问题分析1的表现是一样的，但是将http://gerrit.pt.miui.com/#/c/387000/这个修复cp过来，发现不生效，仍然报错，因此记录一下问题初探测试命令: run gts -m GtsGmscoreHostTestCases -t com.google.android.gts.devicepo...
android cts问题分析,CTS典型问题分析处理
weixin_35555531的博客
05-25 1181
(1) android.net.cts.ListeningPortsTest#testNoListeningPortscts_host > start --plan Android -t android.net.cts.ListeningPortsTest#testNoListeningPortsstart test android.net.cts.ListeningPortsTest#te...
android cts问题分析,一则CTS测试错误分析
weixin_35969257的博客
05-25 676
CTS测试传感器发现失败，具体错误是PackageManager找不到，SensorManager确能找到cts_host > start --plan CTS -t android.app.cts.SystemFeaturesTest#testSensorFeaturesstart test android.app.cts.SystemFeaturesTest#testSensorFeat...
android cts测试方法及步骤详解
08-27
给大家分享了android cts测试方法及步骤的相关知识点，有兴趣的朋友跟着学习习吧。
CTS
03-13
4. 分析结果：根据测试报告，修复发现的问题，然后重新运行CTS以确认问题已解决。 CTS对于维护Android生态系统的健康至关重要，因为它确保了用户可以在各种设备上获得一致的体验，同时也有助于开发者更好地理解如何...
android cts问题分析,CTS问题分析11
weixin_42116847的博客
05-25 1267
CTS/GTS 问题分析11gts case是不放出源码的，这很不方便我们进行问题的分析，如果测试是apk，我们可以通过修改smali重新编译的方式赋值我们分析，那么，如果测试文件是一个jar包，那么应该如何处理呢？以本文为例记录分析方法问题初探测试命令：run gts -m GtsUnofficialApisUsageTestCases -t com.android.gts.api.Unoffi...
cts 测试之AppSecurityTests
ruanjianxiong的专栏
05-23 2544
下面是测试的fial： 下面的部分log: 解决方法： 1.定位到CTS源码的AppSecurityTests类 2.根据测试执行的方法，定位到LOG的具体位置 3.根据位置提示定位到AppSecurityTests类的具体一行 4.得出结果为没有安装相应的APK
android cts 认证测试
chiyingliao3565的博客
06-02 1431
#7.0 run cts -m CtsAccessibilityServiceTestCases -t android.accessibilityservice.cts.AccessibilityWindowQueryTest#testTraverseAllWindows run cts -m...
[Android GMS 认证] STS 问题列表之 android.security.cts.StagefrightTest#testStagefright_bug_34896431
zhms的专栏
10-27 1197
-m CtsSecurityTestCases -t android.security.cts.StagefrightTest#testStagefright_bug_34896431   如下patch即可。 diff --git a/drivers/media/platform/msm/vidc/msm_vdec.c b/drivers/media/platform/msm/vidc/ms...
Android---CTS失败项解析
m0_50408097的博客
06-08 1579
CTS常见失败项
android自动化测试CTS源码分析之四
Jack的博客
04-16 1498
5 测试 流程图如下, CtsTest中的Run方法如下, //获取所有测试项包名 Map> prerequisiteApks = getPrerequisiteApks(mTestPackageList, abiSet); //获取所有测试项的apk Collection uninstallPackages = getPrerequisitePackageNames(mTes
优化MTK Camera性能：解决CTS测试失败问题
本文档提供了针对Camera CTS测试中遇到性能问题的分析和解决策略。" 【详细说明】 1. **测试环境与版本选择**： - 使用合适的系统版本进行测试至关重要。通常推荐使用`userdebug`版本，因为它能够提供更详尽的...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值