Hi Minh,
I noticed this ticket is set as fixed but one question. Looking at the
backtrace in the ticket, it seems
that the imma_cb struct cb_lock mutex is created in thread 5
(avd_imm_reinit_bg_thread)
but in the main thread pthread_mutex_unlock intents to unlock the "old"
cb_lock mutex
but instead uses the new mutex and gets i_code=1, EPERM (ownership of
mutex?). If so, I think this is a problem that we
need to look at.
/Regards HansN
On 07/03/2018 01:25 PM, Minh Chau wrote:
Currently amfd already check @avd_imm_status before setting fd,
amfd should also check @avd_imm_status before calling saImmOiDispatch
---
src/amf/amfd/main.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/amf/amfd/main.cc b/src/amf/amfd/main.cc
index 51a6064..d42fd4e 100644
--- a/src/amf/amfd/main.cc
+++ b/src/amf/amfd/main.cc
@@ -707,7 +707,8 @@ static void main_loop(void) {
avd_d2n_msg_dequeue(cb);
}
- if (cb->immOiHandle && fds[FD_IMM].revents & POLLIN) {
+ if (cb->avd_imm_status == AVD_IMM_INIT_DONE &&
+ cb->immOiHandle && fds[FD_IMM].revents & POLLIN) {
TRACE("IMM event rec");
error = saImmOiDispatch(cb->immOiHandle, SA_DISPATCH_ALL);
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
