Skip to content

Conversation

@jenswi-linaro
Copy link

Until now has kernel private shared memory allocated as dynamic shared
memory (not from the static shared memory pool) been returned if it was
from the static shared memory pool. This causes OP-TEE to refuse the
offered shared memory. Fix this by instead report the shared memory as
any other dynamically allocated shared memory, that is, supply the list
of physical pages which are used.

Fixes: 53a107c ("tee: optee: add registered buffers handling into RPC calls")
Signed-off-by: Jens Wiklander [email protected]

Until now has kernel private shared memory allocated as dynamic shared
memory (not from the static shared memory pool) been returned if it was
from the static shared memory pool. This causes OP-TEE to refuse the
offered shared memory. Fix this by instead report the shared memory as
any other dynamically allocated shared memory, that is, supply the list
of physical pages which are used.

Fixes: 53a107c ("tee: optee: add registered buffers handling into RPC calls")
Signed-off-by: Jens Wiklander <[email protected]>
@jforissier
Copy link

I don't see any patch for this upstream in linux-next, is that expected? Is this still relevant and does this PR need to be merged?

@jenswi-linaro
Copy link
Author

Thanks for the reminder. We can close this. It turned out that the problem only was with single page mappings so we could make some shortcuts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants