Correct potenital locking issue in msg allocation 99/5399/1
authorE. Scott Daniels <daniels@research.att.com>
Fri, 8 Jan 2021 18:57:01 +0000 (13:57 -0500)
committerE. Scott Daniels <daniels@research.att.com>
Fri, 8 Jan 2021 18:57:01 +0000 (13:57 -0500)
commitce1c741c01e8387cb095dac5e36a4d8ad91d006d
tree476007a67b545bd7c12191e83ab6573f5250a294
parentd324fe4bfea9daa22aa16c605bd3157a875a8ccd
Correct potenital locking issue in msg allocation

The message allocation when pulling a buffer from the free pool could
potentially fail to own the lock. This was causing core dumps for
multi-threaded processes (e.g. those using the Go wrapper).

Version bump to 4.5.0 to move away from the previous release of
4.4.*.

Issue-ID: RIC-732

Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I9abc7f64391d0292c5ba1323713040faedb569a1
CHANGES_CORE.txt
CMakeLists.txt
docs/rel-notes.rst
src/rmr/common/include/rmr_agnostic.h
src/rmr/common/src/logging.c
src/rmr/common/src/ring_static.c
src/rmr/si/src/mt_call_si_static.c
src/rmr/si/src/rmr_si.c