Add shared layer API for handling global mutex #476
Description
Is your feature request related to a problem? Please describe.
Currently the shared layer calls OS_Lock_Global_Impl() and OS_Unlock_Global_Impl() directly when locking/unlocking the internal tables within OSAL.
This does not offer a place to:
- check return code of operation
- track ownership of resource in case of not being freed.
Describe the solution you'd like
Should implement OS_Lock_Global() and OS_Unlock_Global() wrappers at the shared API level, which can provide a common place to check status, handle failure, and track resource usage.
Additional context
In #474, the global table lock was correctly returning an error but nothing ever checked the return code. Rather than adding a specific return code test everywhere this is used, simpler and better to add a wrapper.
Requester Info
Joseph Hickey, Vantage Systems, Inc.