Skip to content
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.

Sign up for GitHub

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

Jump to bottom

core: fix access conflict status in rpmb fs that panics TA #1919

Merged
merged 1 commit into from
Nov 8, 2017
Merged

core: fix access conflict status in rpmb fs that panics TA #1919

merged 1 commit into from
Nov 8, 2017

Commits on Nov 7, 2017

  1. core: fix access conflict status in rpmb fs that panics TA 

    According to the GPD TEE Internal Core API specs, when creating
an existing persistent object without the overwrite flag, the OS
should return a TEE_ERROR_ACCESS_CONFLICT status.

This change fixes the RPMB FS layer. An effect of this correction
is that before this change, OS panicked TAs that requested such
forbidden object creation, as a TEE_ERROR_BAD_PARAMETERS return
value is considered by the API as an unexpected status.

Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
Tested-by: Jens Wiklander <jens.wiklander@linaro.org> (QEMU)
    @etienne-lms
    etienne-lms committed Nov 7, 2017
    Configuration menu
    Copy the full SHA
    19b958f View commit details
    Browse the repository at this point in the history