-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
HiKey: xtest 7671 fails (1.0.0-rc2) #494
Comments
To reproduce the issue faster:
|
Merged
cedric-chaumont-st-dev
pushed a commit
to cedric-chaumont-st-dev/optee_os
that referenced
this issue
Oct 13, 2015
Enumeration loop added for object corruption. Add missing free because of tee_svc_storage_set_enum obj_id memory allocation (malloc) during enumeration loop. Force obj_id to NULL in the enumation loop to skip freeing at 'exit' label statement. closes OP-TEE#494 Signed-off-by: Cedric Chaumont <cedric.chaumont@st.com> Tested-by: Cedric Chaumont <cedric.chaumont@linaro.org> (STM boards) Tested-by: Cedric Chaumont <cedric.chaumont@linaro.org> (ARM Juno board) Tested-by: Jerome Forissier <jerome.forissier@linaro.org> (HiKey)
cedric-chaumont-st-dev
pushed a commit
to cedric-chaumont-st-dev/optee_os
that referenced
this issue
Oct 13, 2015
Enumeration loop added for object corruption. Add missing free because of tee_svc_storage_set_enum obj_id memory allocation (malloc) during enumeration loop. Force obj_id to NULL in the enumation loop to skip freeing at 'exit' label statement. closes OP-TEE#494 Signed-off-by: Cedric Chaumont <cedric.chaumont@st.com> Reviewed-by: Jens Wiklander <jens.wiklander@linaro.org> Reviewed-by: Pascal Brand <pascal.brand@linaro.org> Tested-by: Cedric Chaumont <cedric.chaumont@linaro.org> (STM boards)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using https://github.com/OP-TEE/manifest (tag: 1.0.0-rc2) to run the full xtest on HiKey. All tests pass except 7671. And running
xtest 7671
again always fails at this point.Sometimes, the first invocation of
xtest
is successfull (all tests pass) and you have to runxtest
again to get multiple failures. AFAICT all failed tests report some memory allocation error similar to the above trace.Running
xtest 7671
on a freshly booted board shows no error.The text was updated successfully, but these errors were encountered: