Skip to content

Conversation

@rhc54
Copy link
Contributor

@rhc54 rhc54 commented Oct 19, 2016

No description provided.

@rhc54 rhc54 added the bug label Oct 19, 2016
@rhc54 rhc54 added this to the v2.0.2 milestone Oct 19, 2016
peer->index, NULL);
PMIX_RELEASE(peer);
/* remove all registered event handlers so libevent doesn't complain */
PMIX_LIST_FOREACH_SAFE(reginfoptr, regnext, &pmix_server_globals.client_eventregs, pmix_regevents_info_t) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you need a lock around accessing the members of this list? I.e., with a name like "globals", does that imply that another thread may be accessing it at the same time?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, we are in an event and therefore safe from any other thread access

/* remove all registered event handlers so libevent doesn't complain */
PMIX_LIST_FOREACH_SAFE(reginfoptr, regnext, &pmix_server_globals.client_eventregs, pmix_regevents_info_t) {
if (reginfoptr->peer == peer) {
PMIX_RELEASE(reginfoptr);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per IM discussion -- @rhc54 is going to bring over another change here for removing the item from the list.

@hppritcha
Copy link
Member

Travis looks kind of borked up again. I'll give it another 30 minutes

@hppritcha hppritcha merged commit 2515509 into open-mpi:v2.0.x Oct 19, 2016
@rhc54 rhc54 deleted the cmr2.0.x/libevent branch October 31, 2016 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants