qseecom: fix listener_access_lock and unregister issues
When __qseecom_reentrancy_process_incomplete_cmd() calls
__qseecom_process_reentrancy_blocked_on_listener(), it should
first release listener_access_lock, as both of them will take
this mutex inside. Besides, when qseecom processes a pending
listener unregister, it should make sure qseecom_release() is
already called on this listener to avoid free this listener's
private data, which will be used by qseecom_release.
Change-Id: I9dd1937e57f9eaf9d440c13244c66ef9f6771671
Signed-off-by:
Zhen Kong <zkong@codeaurora.org>
Loading
Please register or sign in to comment