Status Update
Comments
vi...@google.com <vi...@google.com> #2
failed in
${AOSP}/device/generic/goldfish-opengl/system/hals/mapper3.cpp
vi...@google.com <vi...@google.com> #3
hw...@kentech.ac.kr <hw...@kentech.ac.kr> #4
NNAPI VTS wrong usage?
Yes. Our gralloc passed CtsNativeHardwareTestCases and CtsGraphicsTestCases.
vi...@google.com <vi...@google.com> #5
thanks, I will try to modify NNAPI code.
vi...@google.com <vi...@google.com> #6
I don't know how to close this issue.
hw...@kentech.ac.kr <hw...@kentech.ac.kr> #7
Hi teams, As attend picture, function comment says if buffer format is AHARDWAREBUFFER_FORMAT_BLOB, it can be locked with read/write simultaneously. So I think NNAPI is not wrong. Android I check CtsNativeHardwareTestCases and CtsGraphicsTestCases source code, I didn't find testcase about "AHARDWAREBUFFER_FORMAT_BLOB" lock in different thread or process. Can someone help on this?
hw...@kentech.ac.kr <hw...@kentech.ac.kr> #8
Can NNAPI association team also have a look on this? nnapi AHardwareBuffer is AHARDWAREBUFFER_FORMAT_BLOB
hw...@kentech.ac.kr <hw...@kentech.ac.kr> #9
I didn't find testcase about "AHARDWAREBUFFER_FORMAT_BLOB" lock in different thread or process.
You can't lock for reading in one thread and for writing in another thread. You can lock for reading+writing in one thread and to use as regular memory. Once you unlock it, you can use it in another place.
vi...@google.com <vi...@google.com> #10
raise another issue for Nnapi at
Description
Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (
Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes
=====
Dear,
I am Hyunwoo Lee, an assistant professor at KENTECH in South Korea.
I was a postdoc at Purdue from 2020-2022 and I and my colleagues at Purdue developed the security testing framework for the VoWiFi smartphones.
With it, we have analyzed security of VoWiFi android phones and have found some issues.
We want to share the result with you. Most of the issues are not directly related to the Android framework, but we are reporting the results because those phones are running over Android and just in case there is something that we have missed.
I have shared the report with android-bugreport@google.com through Google Drive.
Please let me know if it does not work or if you have any question.
Sincerely,
Hyunwoo Lee.
Security_Issues_of_VoWiFi_Android_Smartphones.pdf -