commit fd10f62b821033f20d6fdc73cfd804d18806b46d
author Ovidiu Mihalachi <ovidiu_mihalachi@mentor.com> Mon Jan 28 13:01:24 2019 +0200
committer Jérôme Forissier <jerome.forissier@linaro.org> Tue May 07 16:16:24 2019 +0200
tree ae1db8f1a4d93728c0442f47eaed99dcb5e4ea09
parent 6e59bb1e95f0b3334d2f06a1312e9e395bb1232c

core: keep alive TA context can be created after TA has panicked

When a keep alive TA instance panics, it continues to exist and
blocks all further use of the TA until the next reboot of the system.
Moreover, when a new session is trying to be created for
the panicked TA (while another session to that TA is still opened),
the system hangs.

This change releases panicked TA context and clears all references to
the released context when the TA panics regardless the TA properties.
This allows keep alive TA instances to be created back after they have
panicked without needing to reboot OP-TEE core.

Sessions on panicked TAs have to be closed by the client by calling
the proper API when session client is scheduled back.

Signed-off-by: Ovidiu Mihalachi <ovidiu_mihalachi@mentor.com>
Reviewed-by: Etienne Carriere <etienne.carriere@linaro.org>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>