-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TA to TA communication results in segfault #28
Comments
There was a bug related to TA2TA communication and TEE_TYPE_MEMREF_XXXX, but it did not end up to segfault. The fix has been committed into tee-engine-repository. Would you be able to provide reproducing steps? Unfortunately currently OpenTEE allows ta2ta communication when connection is established and therefore it is possible only within "TA_InvokeCommandEntryPoint"-function. It needs a bit investigating whether it is feasible to add other entrypoint-functions. As a trivia then "4.9 Internal Client API"-chapter has been in since TEE Internal Core API v1.0 (I guess from the first spec). A bug fix tee-engine A basic smoke test for TA2TA communication |
@TanelDettenborn With the latest code, I see the following observation. Please consider the following patch which fixes the issue.
|
@hkandiga Above patch might be enough, but I will think through and try to get the patch in as soon as possible! |
from one TA to another TA results in segfault during TEE_InvokeTACommand
I know that the APIs for TEE_OpenSession, TEE_InvokeTACommand have been added since "TEE Internal Core API v1.2".
Just wanted to know if there any plan to support the TA to TA communication?
The text was updated successfully, but these errors were encountered: