Skip to content

Conversation

@thananon
Copy link
Member

@thananon thananon commented Aug 3, 2016

This commits changed rand() and family in libevent to use internal random function provided in opal to prevent pertubing user's random seed. (from issue #1877)

Again, this will not solve the problem if the user use their own external libevent.

Modified from @ggouaillardet patch.

@jsquyres
Copy link
Member

jsquyres commented Aug 3, 2016

@Di0gen @artpol84 @jladd-mlnx Can you please look at this Mellanox Jenkins failure?

17:22:40 configure: error: HCOLL support requested but not found.  Aborting


# We added this in order to enforce the use of internal random
# function to prevent pertubing the random seed of the user.
# libevent uses random function in poll(), select() and evutil().
Copy link
Member

Choose a reason for hiding this comment

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

Slightly tweak the wording:

We define "random" to be "opal_random" so that Libevent will not use random(3) internally (and potentially unexpectedly perturb values returned by rand(3) to the application).

@jsquyres
Copy link
Member

jsquyres commented Aug 3, 2016

Please use a git commit message as described here: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

@jsquyres
Copy link
Member

jsquyres commented Aug 3, 2016

Please also put "Fixes #1877" in the commit message so that when this PR is merged, it will auto-close #1877.

@artpol84
Copy link
Contributor

artpol84 commented Aug 3, 2016

@jsquyres checking

@jsquyres
Copy link
Member

jsquyres commented Aug 3, 2016

Just to cross-reference: Ralph filed this issue upstream with libevent: libevent/libevent#384

This commits changed rand(3) and family in libevent to use internal
random function provided in opal to prevent pertubing user's random seed.

Fixes open-mpi#1877
@jsquyres jsquyres merged commit 36555b7 into open-mpi:master Aug 4, 2016
@jsquyres
Copy link
Member

jsquyres commented Aug 4, 2016

@thananon Please PR this to v2.0.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants