arm: optee: don't print warning about "wrong" RPC buffer
authorVolodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Mon, 5 Oct 2020 09:12:32 +0000 (09:12 +0000)
committerStefano Stabellini <sstabellini@kernel.org>
Tue, 20 Oct 2020 20:20:28 +0000 (13:20 -0700)
commitaace5466996e743a087153ad3f9d8fcf11a76c56
tree950fff2d7009487cf53188a4d33c522843a3c1a9
parent0514a3a25fb9ebff5d75cc8f00a9229385300858
arm: optee: don't print warning about "wrong" RPC buffer

The OP-TEE mediator tracks the cookie value of the last buffer which was
requested by OP-TEE. This tracked value serves one important purpose: if
OP-TEE wants to request another buffer, we know that it finished
importing the previous one and we can free the page list associated with
it.

Also, we had a false premise that OP_TEE frees requested buffers in
reversed order. So we checked rpc_data_cookie during handling of the
OPTEE_RPC_CMD_SHM_FREE call and printed a warning if the cookie of the
buffer which is requested to be freed differs from the last allocated
one.

During testing of RPMB FS services I discovered that RPMB code frees
request and response buffers in the same order is it allocated them. And
this is perfectly fine, actually.

So, we are removing mentioned warning message in Xen, as it is perfectly
normal to free buffers in arbitrary order.

Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
[stefano: fix grammar]
Signed-off-by: Stefano Stabellini <stefano.stabellini@xilinx.com>
xen/arch/arm/tee/optee.c