dump与strace命令实战之分析keystore死锁导致watchdog问题

已于 2023-11-14 17:35:02 修改
阅读量404 收藏 2
点赞数
文章标签： android linux
于 2023-10-29 19:20:37 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/suixin______/article/details/134105995
版权

一、问题描述

近期发生一个系统卡死的问题。推测是system_server出现watchdog。查看watchdog文件，是PackageManager卡在了KeyStore.clearUid()接口：


----- pid 1091 at 2023-10-26 09:40:10 -----
Cmd line: system_server
ABI: 'arm64'

"PackageManager" sysTid=1352
  #00 pc 000000000006e1c4  /system/lib64/libc.so (__ioctl+4)
  #01 pc 00000000000290d0  /system/lib64/libc.so (ioctl+136)
  #02 pc 000000000005a5e4  /system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+256)
  #03 pc 000000000005b48c  /system/lib64/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+340)
  #04 pc 000000000005b1c0  /system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+176)
  #05 pc 0000000000051318  /system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+72)
  #06 pc 000000000012f72c  /system/lib64/libandroid_runtime.so (android_os_BinderProxy_transact(_JNIEnv*, _jobject*, int, _jobject*, _jobject*, int)+152)
  #07 pc 0000000000406e34  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.BinderProxy.transactNative+196)
  #08 pc 0000000000c00d5c  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.BinderProxy.transact+748)
  #09 pc 000000000065e4e8  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.security.IKeystoreService$Stub$Proxy.clear_uid+216)
  #10 pc 0000000000556578  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.security.KeyStore.clearUid+88)
  #11 pc 00000000014bdba4  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.removeKeystoreDataIfNeeded+244)
  #12 pc 00000000014bea94  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.removePackageDataLIF+2836)
  #13 pc 00000000014900b0  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.deleteInstalledPackageLIF+688)
  #14 pc 000000000149161c  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.deletePackageLIF+3532)
  #15 pc 00000000014dd554  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.deletePackageX+2724)
  #16 pc 0000000000d9735c  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService$12.run+476)
  #17 pc 0000000000ab737c  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.Handler.dispatchMessage+76)
  #18 pc 0000000000aba4e0  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.Looper.loop+1264)
  #19 pc 0000000000ab9380  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.HandlerThread.run+544)
  #20 pc 00000000007d57b4  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.ServiceThread.run+100)
  #21 pc 0000000000554d88  /system/lib64/libart.so (art_quick_invoke_stub+584)
  #22 pc 00000000000cf6c8  /system/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+200)
  #23 pc 000000000045c840  /system/lib64/libart.so (art::(anonymous namespace)::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art::(anonymous namespace)::ArgArray*, art::JValue*, char const*)+104)
  #24 pc 000000000045d8fc  /system/lib64/libart.so (art::InvokeVirtualOrInterfaceWithJValues(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, jvalue*)+424)
  #25 pc 0000000000488a94  /system/lib64/libart.so (art::Thread::CreateCallback(void*)+1120)
  #26 pc 00000000000819b4  /system/lib64/libc.so (__pthread_start(void*)+36)
  #27 pc 0000000000023478  /system/lib64/libc.so (__start_thread+68)

出现问题的场景是在应用商店安装卸载某些应用。经过后面调查，在安装删除某个应用后，即出现这个问题。使用adb uninstall 该应用可以发现命令行一直卡在卸载中，没有正常返回。

经过代码走读，keystore服务注册的线程池为1。删除这个应用时候如果keystoreservice卡住了，则后面调用keystoreservice接口的模块也必定会卡住。

二，使用strace命令

8155平台keystoreservice是android的。keymaster是高通的qtikeymaster。于是写下面三个批处理命令，跟踪system_server, keystoreservice, qtikeymaster的系统调用情况。

1，写一个如下的批处理程序 strace_keystore.bat，开始捕获keystore与keymaster的系统调用。

echo "enable adb connecting first..."

adb wait-for-device
adb root

echo Wscript.sleep Wscript.Arguments(0)>Delay.vbs
Delay.vbs 5000
del Delay.vbs

adb shell mkdir /data/strace

md d:\stracelog

adb shell "echo 512 > /sys/module/binder/parameters/debug_mask"

adb shell pidof android.hardware.keymaster@4.0-service-qti > d:\stracelog\keymaster.pid

adb shell pidof keystore > d:\stracelog\keystore.pid

adb shell "strace -p `pidof keystore` -p `pidof  android.hardware.keymaster@4.0-service-qti` -o /data/strace/process -f -ff -tt"

上面命令会把trace log保存在系统/data/strace目录。本地windows目录d:\stracelog文件夹保存出现问题时候keystore与keymaster的进程后，便于后面导出/data/strace/目录LOG后确认进程。

2，通过adb uninstall com.xxx.car复现该问题。

3，写一个 export_strace_logs.bat 批处理程序导出LOG。

adb pull /data/strace/ d:\stracelog
adb shell "rm /data/strace/*"

4，同时导出adb log。

5，分析strace log看，最后keystore卡在了：

09:47:17.190694 ioctl(4, BINDER_WRITE_READ, 0x7ff422e268) = 0
09:47:17.199964 ioctl(7, BINDER_WRITE_READ, 0x7ff4236a78) = 0
09:47:17.200665 futex(0x7339a462c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
09:47:17.200762 ioctl(7, BINDER_WRITE_READ, 0x7ff4236ca8) = 0
09:47:17.200844 futex(0x7339a462c8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
09:47:17.200929 newfstatat(AT_FDCWD, "timestamp", {st_mode=S_IFREG|0600, st_size=0, ...}, 0) = 0
09:47:17.201304 ioctl(7, BINDER_WRITE_READ, 0x7ff422e138) = 0
09:47:17.201724 mprotect(0x73bbd6e000, 4096, PROT_READ|PROT_WRITE) = 0
09:47:17.201806 mprotect(0x73bbd6e000, 4096, PROT_READ) = 0
09:47:17.202226 futex(0x73bb575080, FUTEX_WAKE_PRIVATE, 2147483647) = 0
09:47:17.202310 ioctl(7, BINDER_WRITE_READ, 0x7ff422e208) = 0
09:47:17.203316 faccessat(AT_FDCWD, "user_0/10041_USRPKEY_no506b3822wb", R_OK|W_OK) = 0
09:47:17.203436 openat(AT_FDCWD, "user_0/10041_USRPKEY_no506b3822wb", O_RDONLY) = 9
09:47:17.203536 read(9, "\3\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32824) = 823
09:47:17.203612 read(9, "", 32001)      = 0
09:47:17.203670 close(9)                = 0
09:47:17.203756 ioctl(4, BINDER_WRITE_READ

这个是不正常的，这种情况预示这正在等待binder对端的返回。如果是平时的空闲态，则进程的最后打印应该阻塞在如下代码：

00:05:07.682578 ioctl(7, BINDER_WRITE_READ <detached ...>

继续查看qtikeymaster的strace log:

9:47:17.205302 close(6)                = 0
09:47:17.205372 madvise(0x765dcb4000, 102400, MADV_DONTNEED) = 0
09:47:17.205447 madvise(0x765dc92000, 102400, MADV_DONTNEED) = 0
09:47:17.205526 openat(AT_FDCWD, "/dev/hab", O_RDWR) = 6
09:47:17.205613 ioctl(6, _IOC(_IOC_READ|_IOC_WRITE, 0xa, 0x4, 0x10), 0x7fe6247b68) = 0
09:47:17.206340 getuid()                = 1000
09:47:17.206412 writev(5, [{iov_base="\0a\1\245s8e\351,J\f", iov_len=11}, {iov_base="\4", iov_len=1}, {iov_base="uhab\0", iov_len=5}, {iov_base="habmm_socket_open: opened fd 6, "..., iov_len=67}], 4) = 84
09:47:17.206709 ioctl(6, _IOC(_IOC_WRITE, 0xa, 0x2, 0x18), 0x7fe6247b70) = 0
09:47:17.206960 ioctl(6, _IOC(_IOC_READ|_IOC_WRITE, 0xa, 0x3, 0x18)

最后也是卡在ioctl接口的一个read函数。这个函数没有返回值，说明在卡着。由于keystoreservice也是qtikeymaster的一个client，security环境是厂家实现的。卡在了qtikeymaster。

三、确认卡在哪个接口

通过在system/security/keystore/key_store_service.cpp 加LOG，最后确认了，问题APP在联网与不联网情况下初始化时候调用的keystore接口是不一样的：

可联网场景安装：
keystore: del USRPKEY_CMCC_SDK
keystore: del USRCERT_CMCC_SDK
keystore: del CACERT_CMCC_SDK
keystore: del USRPKEY_no506b3822wb
keystore: del USRCERT_no506b3822wb
keystore: del CACERT_no506b3822wb
keystore: attestKey
keystore: del USRPKEY_sec506b3822
keystore: del USRCERT_sec506b3822
keystore: del CACERT_sec506b3822
有网络卸载：
keystore: clear_uid
无网络安装：
keystore: del USRPKEY_CMCC_SDK
keystore: del USRCERT_CMCC_SDK
keystore: del CACERT_CMCC_SDK
无网络卸载：
keystore: clear_uid

最后卡住的接口是keystore: attestKey。问了确认调用函数栈，我们需要命令来在卡住时候打印调用栈：

dump1_system_server.bat

adb shell "debuggerd -b  `pidof system_server`" >d:\stracelog\dump_system_server.txt

dump2_keystore.bat

adb shell "debuggerd -b  `pidof keystore`" >d:\stracelog\dump_keystore.txt

dump3_keymaster.bat

adb shell "debuggerd -b `pidof  android.hardware.keymaster@4.0-service-qti` " >d:\stracelog\dump_keymaster.txt

注意，debuggerd -b 命令是会让当前进程退出block状态继续往下进行的。所以如果锁有嵌套关系，要先dump出来外层的应该用，后dump根层的应用。所以本例中dump的顺序是先system_server，最后是qtikeymaster.

dump的结果是：

----- pid 962 at 2023-10-26 20:47:27 -----
Cmd line: system_server
ABI: 'arm64'


"PackageManager" sysTid=1121
  #00 pc 000000000006e1c4  /system/lib64/libc.so (__ioctl+4)
  #01 pc 00000000000290d0  /system/lib64/libc.so (ioctl+136)
  #02 pc 000000000005a5e4  /system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+256)
  #03 pc 000000000005b48c  /system/lib64/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+340)
  #04 pc 000000000005b1c0  /system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+176)
  #05 pc 0000000000051318  /system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+72)
  #06 pc 000000000012f72c  /system/lib64/libandroid_runtime.so (android_os_BinderProxy_transact(_JNIEnv*, _jobject*, int, _jobject*, _jobject*, int)+152)
  #07 pc 0000000000406e34  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.BinderProxy.transactNative+196)
  #08 pc 0000000000c00d5c  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.BinderProxy.transact+748)
  #09 pc 000000000065e4e8  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.security.IKeystoreService$Stub$Proxy.clear_uid+216)
  #10 pc 0000000000556578  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.security.KeyStore.clearUid+88)
  #11 pc 00000000014bdba4  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.removeKeystoreDataIfNeeded+244)
  #12 pc 00000000014bea94  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.removePackageDataLIF+2836)
  #13 pc 00000000014900b0  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.deleteInstalledPackageLIF+688)
  #14 pc 000000000149161c  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.deletePackageLIF+3532)
  #15 pc 00000000014dd554  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService.deletePackageX+2724)
  #16 pc 0000000000d97634  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.pm.PackageManagerService$12.run+1204)
  #17 pc 0000000000ab737c  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.Handler.dispatchMessage+76)
  #18 pc 0000000000aba4e0  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.Looper.loop+1264)
  #19 pc 0000000000ab9380  /system/framework/arm64/boot-framework.oat (offset 0x3d2000) (android.os.HandlerThread.run+544)
  #20 pc 00000000007d57b4  /system/framework/oat/arm64/services.odex (offset 0x64d000) (com.android.server.ServiceThread.run+100)
  #21 pc 0000000000554d88  /system/lib64/libart.so (art_quick_invoke_stub+584)
  #22 pc 00000000000cf6c8  /system/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+200)
  #23 pc 000000000045c840  /system/lib64/libart.so (art::(anonymous namespace)::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art::(anonymous namespace)::ArgArray*, art::JValue*, char const*)+104)
  #24 pc 000000000045d8fc  /system/lib64/libart.so (art::InvokeVirtualOrInterfaceWithJValues(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, jvalue*)+424)
  #25 pc 0000000000488a94  /system/lib64/libart.so (art::Thread::CreateCallback(void*)+1120)
  #26 pc 00000000000819b4  /system/lib64/libc.so (__pthread_start(void*)+36)
  #27 pc 0000000000023478  /system/lib64/libc.so (__start_thread+68)





----- pid 904 at 2023-10-26 20:47:30 -----
Cmd line: /system/bin/keystore
ABI: 'arm64'

"keystore" sysTid=904
  #00 pc 000000000006e1c4  /system/lib64/libc.so (__ioctl+4)
  #01 pc 00000000000290d0  /system/lib64/libc.so (ioctl+136)
  #02 pc 000000000001cfdc  /system/lib64/libhwbinder.so (android::hardware::IPCThreadState::talkWithDriver(bool)+240)
  #03 pc 000000000001e018  /system/lib64/libhwbinder.so (android::hardware::IPCThreadState::waitForResponse(android::hardware::Parcel*, int*)+60)
  #04 pc 000000000001cce4  /system/lib64/libhwbinder.so (android::hardware::BpHwBinder::transact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+132)
  #05 pc 00000000000148e8  /system/lib64/android.hardware.keymaster@4.0.so (android::hardware::keymaster::V4_0::BpHwKeymasterDevice::_hidl_attestKey(android::hardware::IInterface*, android::hardware::details::HidlInstrumentor*, android::hardware::hidl_vec<unsigned char> const&, android::hardware::hidl_vec<android::hardware::keymaster::V4_0::KeyParameter> const&, std::__1::function<void (android::hardware::keymaster::V4_0::ErrorCode, android::hardware::hidl_vec<android::hardware::hidl_vec<unsigned char>> co  #06 pc 00000000000184d8  /system/lib64/android.hardware.keymaster@4.0.so (android::hardware::keymaster::V4_0::BpHwKeymasterDevice::attestKey(android::hardware::hidl_vec<unsigned char> const&, android::hardware::hidl_vec<android::hardware::keymaster::V4_0::KeyParameter> const&, std::__1::function<void (android::hardware::keymaster::V4_0::ErrorCode, android::hardware::hidl_vec<android::hardware::hidl_vec<unsigned char>> const&)>)+160)
  #07 pc 00000000000482c4  /system/bin/keystore (android::hardware::keymaster::V4_0::support::Keymaster4::attestKey(android::hardware::hidl_vec<unsigned char> const&, android::hardware::hidl_vec<android::hardware::keymaster::V4_0::KeyParameter> const&, std::__1::function<void (android::hardware::keymaster::V4_0::ErrorCode, android::hardware::hidl_vec<android::hardware::hidl_vec<unsigned char>> const&)>)+212)
  #08 pc 000000000003d604  /system/bin/keystore (keystore::KeyStoreService::attestKey(android::String16 const&, android::security::keymaster::KeymasterArguments const&, android::security::keymaster::KeymasterCertificateChain*, int*)+832)
  #09 pc 0000000000016554  /system/lib64/libkeystore_aidl.so (android::security::BnKeystoreService::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+1432)
  #10 pc 000000000004fa60  /system/lib64/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+136)
  #11 pc 000000000005ab00  /system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+520)
  #12 pc 000000000005a83c  /system/lib64/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+156)
  #13 pc 000000000005af04  /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+60)
  #14 pc 0000000000049484  /system/bin/keystore (main.cfi+1364)
  #15 pc 00000000000acac8  /system/lib64/libc.so (__libc_init+88)

"HwBinder:904_1" sysTid=941
  #00 pc 000000000006e1c4  /system/lib64/libc.so (__ioctl+4)
  #01 pc 00000000000290d0  /system/lib64/libc.so (ioctl+136)
  #02 pc 000000000001cfdc  /system/lib64/libhwbinder.so (android::hardware::IPCThreadState::talkWithDriver(bool)+240)
  #03 pc 000000000001425c  /system/lib64/libhwbinder.so (android::hardware::IPCThreadState::getAndExecuteCommand()+20)
  #04 pc 0000000000014588  /system/lib64/libhwbinder.so (android::hardware::IPCThreadState::joinThreadPool(bool)+268)
  #05 pc 000000000001c1ac  /system/lib64/libhwbinder.so (android::hardware::PoolThread::threadLoop()+24)
  #06 pc 000000000000f9d8  /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+280)
  #07 pc 00000000000819b4  /system/lib64/libc.so (__pthread_start(void*)+36)
  #08 pc 0000000000023478  /system/lib64/libc.so (__start_thread+68)

----- end 904 -----


----- pid 354 at 2023-10-26 20:47:33 -----
Cmd line: /vendor/bin/hw/android.hardware.keymaster@4.0-service-qti
ABI: 'arm64'

"keymaster@4.0-s" sysTid=354
  #00 pc 000000000006e1c8  /system/lib64/libc.so (__ioctl+8)
  #01 pc 00000000000290d0  /system/lib64/libc.so (ioctl+136)
  #02 pc 0000000000001260  /vendor/lib64/libuhab.so (habmm_socket_recv+96)
  #03 pc 0000000000002150  /vendor/lib64/libkeymasterdeviceutils.so (km_comm_send_cmd+444)
  #04 pc 000000000000cd00  /vendor/lib64/libqtikeymaster4.so (keymasterdevice::KeymasterHalDevice::attest_key(keymaster_key_blob_t const*, keymaster_key_param_set_t const*, keymaster_cert_chain_t*)+892)
  #05 pc 000000000000919c  /vendor/lib64/libqtikeymaster4.so (keymaster::V4_0::Keymaster4Device::attestKey(android::hardware::hidl_vec<unsigned char> const&, android::hardware::hidl_vec<android::hardware::keymaster::V4_0::KeyParameter> const&, std::__1::function<void (android::hardware::keymaster::V4_0::ErrorCode, android::hardware::hidl_vec<android::hardware::hidl_vec<unsigned char>> const&)>)+132)
  #06 pc 000000000001bf18  /system/lib64/vndk-28/android.hardware.keymaster@4.0.so (android::hardware::keymaster::V4_0::BnHwKeymasterDevice::_hidl_attestKey(android::hidl::base::V1_0::BnHwBase*, android::hardware::Parcel const&, android::hardware::Parcel*, std::__1::function<void (android::hardware::Parcel&)>)+484)
  #07 pc 000000000001e820  /system/lib64/vndk-28/android.hardware.keymaster@4.0.so (android::hardware::keymaster::V4_0::BnHwKeymasterDevice::onTransact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+2048)
  #08 pc 000000000001d334  /system/lib64/vndk-sp-28/libhwbinder.so (android::hardware::IPCThreadState::executeCommand(int)+640)
  #09 pc 000000000001430c  /system/lib64/vndk-sp-28/libhwbinder.so (android::hardware::IPCThreadState::getAndExecuteCommand()+196)
  #10 pc 0000000000014588  /system/lib64/vndk-sp-28/libhwbinder.so (android::hardware::IPCThreadState::joinThreadPool(bool)+268)
  #11 pc 0000000000000f64  /vendor/bin/hw/android.hardware.keymaster@4.0-service-qti (main+128)
  #12 pc 00000000000acac8  /system/lib64/libc.so (__libc_init+88)

----- end 354 -----

最后就是让qtikeymaster查:

keymasterdevice::KeymasterHalDevice::attest_key

四、QSEE log

QSEE下面，需要把tz log导出来给高通分析。tz log可以在问题复现的时候，在QNX终端敲命令获取：

cat /dev/pdbg/qcore/tzdiag/qseecom
cat /dev/pdbg/qcore/tzdiag/log

张和阳
关注
  • 0
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
JDK的sql设计不合理导致的驱动类初始化死锁问题
02-25
这篇文章是使用我们生产环境的一个系统的线程dump和内存dump为基础进行分析展开的。当我们一个系统既需要mysql驱动，也需要oracle驱动的时候，在并发加载初始化这些驱动类的过程中产生死锁的可能性非常大，下面是一...
android进阶之Watchdog检查系统异常机制
XuJiaoJie的博客
01-18 2151
Watchdog简介Watchdog是Android系统提供的以后总检查系统异常的机制，正如其名，“看门狗”，它看的是Android框架层的几个核心服务。Watchdog一旦发现的AMS、WMS和PMS等核心服务的主线程阻塞，就清除systemserver进程，我们知道，一单SystemServer进程停止，Zygote进程就会自杀，系统就会重启。Watchdog继承Thread，它是一个线程类，它...
Java Security：keytool工具使用说明
weixin_33857679的博客
02-01 578
Keytool用法说明 Keytool是一个key与cert的管理工具。使用keytool可以管理public key、private key，以及与key之相关的certificate。   1、command和option说明 1.1 command 使用keytool工具时，可以使用15种命令：     1.2 option Option是命令的参数，要了解某个命令的参数可...
Android跨进程调用，Binder线程池溢出导致ANR
最新发布
weixin_46039528的博客
06-25 403
sysTid=1863是进程号，ANR发生在at android.os.BinderProxy.transactNative(Native method)，在transcatNative函数中，transcatNative 函数式客户端发起端的函数，猜测这是Binder卡住，客户端等待响应中，这种问题基本上就是我们在跨进程通信调用服务端的时候太频繁了，大部分原因是由于业务逻辑，才会写这种代码，解决办法就是降低调用的频率，或者延迟调用，设置一些时间间隔，app端不要频繁调用服务端。
高通Secure Boot调试流程记录
King_Guo的博客
07-07 6668
参考文档KBA-161109181347-how_to_enable_secure_boot_step_by_step.pdf。 1.新建临时目录tmp：    mkdir tmp    cd tmp 2.复制opensslroot.cfg和v3.ext到tmp目录，这两个文件在后面的命令中要用到：    cp ~/work/M1503-6.0.1-01610/LINUX/android
android 性能问题详解
QinQin_92的专栏
03-19 3387
系统的性能问题 Android SWT ： Android Software Watchdog Timeout 作用：监控核心服务和核心线程是否卡住，如果判断阻塞 60s ,就会把系统重启，来保证系统恢复正常状态. 应用的性能问题 ANR ANR弹出对话框提示用户 InputDispatching Timeout：5秒内无法响应屏幕触摸事件或键盘输入事件 BroadcastQueue Timeout ：在执行前台广播（BroadcastReceiver）的onReceive()函数时10秒没
QCS2290 secureboot 流程
weixin_42265250的博客
05-19 1604
QCS2290 secureboot 流程分析
熔丝相关的sec.dat怎么判断和签名的证书是否一致的问题
weixin_32104133的博客
09-09 1928
推荐两篇文档，签名熔丝相关的非常不错的文档。 强烈推荐学习一下 https://www.anquanke.com/post/id/162191 ，这篇文档详细介绍了sec.dat生成的过程。 https://blog.csdn.net/armfpga123/article/details/65446628### ，这篇文档详细介绍了高通msm8909平台实现签名的流程。 本文只是简单介绍一下怎么验...
windbg-x64 dump分析工具
01-16
Windbg是在windows平台下，强大的用户态和内核态调试工具。相比较于Visual Studio，它是一个轻量级的调试工具，所谓轻量级指的是它的安装文件大小较小，但是其调试功能，却...它的另外一个用途是可以用来分析dump数据。
如何通过jstack命令dump线程信息
10-15
在遇到死锁问题时，`jstack`会显示出死锁的详细信息。死锁是指两个或多个线程互相持有对方需要的资源，导致它们都无法继续执行。就像上面的代码示例，线程`t1`持有锁A，尝试获取锁B，而线程`t2`持有锁B，尝试获取锁A...
Linux dump命令用法详解
01-09
Linux dump命令 Linux dump命令用于备份文件系统。 dump为备份工具程序，可将目录或整个文件系统备份至指定的设备，或备份成一个大文件。 语法 dump [-cnu][-0123456789][-b ][-B ][-d ][-f ][-h ][-s ][-T ][目录...
高通平台获取QSEE 日志
xiezhi123456的博客
09-26 3640
1、cat /sys/kernel/debug/tzdbg/qsee_log  2、cat /d/tzdbg/log 3、cat /d/tzdbg/qsee_log
keystore2代码导读笔记
baron-周贺贺-代码改变世界ctw
06-07 1172
setWrappedKeyEntry – AndroidKeyStoreSpi.javaIKeystoreSecurityLevel.aidlimport_key – system/security/keystore2/src/security_level.rskm_dev.importKey(&params, format, key_data, None /* attestKey */) — 调用到Vendor HAL---->TA
Androrid KeyStore, KeyStore TA （二）
求变，从思想开始
05-31 3200
目标Android Keystore API 和底层 Keymaster HAL 提供了一套基本的但足以满足需求的加密基元，以便使用访问受控且由硬件支持的密钥实现相关协议。除了扩大加密基元的范围外，Android 6.0 中的 Keystore 还增加了以下内容：·        一个使用控制方案，用于限制密钥的使用，并降低因滥用密钥而损害安全性的风险·        一个访问控制方案，用于限定只...
安装证书相关流程及keystore存储机制
yunajie's blog
09-22 3067
锁定区验证机制升级@[锁定区|验证] 锁定区存在的的问题 目前验证机制为白名单验证机制，带来两个方面的问题： 在白名单里的应用可以直接访问锁定区的照片和视频及其他文件，导致用户不想公开的文件泄露 第三方应用无法访问锁定区，在用户体验上不够好升级锁定区验证机制，解决上面两个问题 解决方案： 本着最小代码修改的原则，在现有机制上加入第二验证机制。直白点讲就是，文档作为访问锁定区唯
AndroidKeyStore管理及实现-基于源码7.1.1.r13
wuawua1的博客
12-08 3608
一、   Java层代码实现及调用 1.       Apps接口调用—证书导入apk (1)       代码路径为：packages/apps/Settings/src/com/android/settings/CredentialStorage.java (2)       功能为UNLOCK/ INSTALL/ RESET 通过调用android.security.keystore
人脸解锁带来的安卓系统崩溃之谜！
嵌入式Linux
11-05 194
问题背景用户反馈开启人脸解锁后，偶现密码解锁、指纹解锁、人脸解锁均无法使用，系统卡死随后出现安卓重启。问题分析SWT之初步释疑查看android SWT(Software Watchdog Timeout)日志，发现android.ui线程卡死。1Subject: Blocked in handler on ui thread (android.ui)查看android.ui堆栈，可以看到该线程一...
android 4.0的模板,Android keymaster4.0- device集成笔记
weixin_39613089的博客
05-31 571
快速链接:.???????????? 个人博客笔记导读目录(全部) ????????????相关推荐:1、Android keymaster的介绍和总结2、Android keystore/Keymaster的代码导读文章目录1、keymaster@4.0-service的集成2、keymaster HAL接口的定义3、keymaster@4.0-service 纯软实现3、keymaster@4.0-service beanpod...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值