-
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
Rpmb fix #1921
Rpmb fix #1921
Conversation
Fixes #1780 |
For "core: RPMB_FS: remember owner uuid", with the proper 12-character SHA1 prefix in the commit description: |
FYI, "core: RPMB_FS: remember owner uuid" has a proper 12-character SHA1 prefix in the commit description, it's just github mangling the commit message. |
Ah, yes indeed, but checkpatch expects "commit 078f18f ..." (the word "commit" has to be there). |
Message updated, tag applied |
#1919 is updated (tag applied) |
@jenswi-linaro can you please rebase now that 1919 is merged? Thanks. |
Prior to this patch was the owning uuid looked up via the current session. The assumption that the uuid of the context of the current session is the same as the owner of a RPMB file doesn't hold any longer after: commit 078f18f ("core: RPMB FS: provide tee_rpmb_fs_raw_open()") was introduced. Instead the pointer to the uuid passed as the owner is stored in the file handle and used as needed when encrypting/decrypting the file. Acked-by: Jerome Forissier <[email protected]> Fixes: OP-TEE#1780 Tested-by: Jens Wiklander <[email protected]> (QEMU) Signed-off-by: Jens Wiklander <[email protected]>
Rebased |
For all tests to pass #1919 is needed too, please ignore
"core: fix access conflict status in rpmb fs that panics TA" while reviewing this PR