{"push_id":783951088,"size":2,"distinct_size":2,"ref":"refs/heads/v4.0.0-rc","head":"c17ed0679ed1842c12a7a2f5df82fb300308f742","before":"6efb69711dfda38ab068f249ebb92698e55f7cd1","commits":[{"sha":"337e1e0da3b4a52ac1e4671260dbf1de28fc7e44","author":{"email":"59bd0a3ff43b32849b319e645d4798d8a5d1e889@bnoordhuis.nl","name":"Ben Noordhuis"},"message":"crypto: replace rwlocks with simple mutexes\n\nIt was pointed out by Zhou Ran that the Windows XP implementation of\nuv_rwlock_rdlock() and friends may unlock the inner write mutex on a\ndifferent thread than the one that locked it, resulting in undefined\nbehavior.\n\nThe only place that uses rwlocks is the crypto module.  Make that use\nnormal (simple) mutexes instead.\n\nOpenSSL's critical sections are generally very short, with exclusive\naccess outnumbering shared access by a factor of three or more, so\nit's not as if using rwlocks gives a decisive performance advantage.\n\nPR-URL: https://github.com/nodejs/node/pull/2723\nReviewed-By: Fedor Indutny <fedor@indutny.com>","distinct":true,"url":"https://api.github.com/repos/nodejs/node/commits/337e1e0da3b4a52ac1e4671260dbf1de28fc7e44"},{"sha":"c17ed0679ed1842c12a7a2f5df82fb300308f742","author":{"email":"ad0310dc5270cefb6ee6879263270aed9b1e9982@me.com","name":"Evan Lucas"},"message":"child_process: use stdio.fd even if it is 0\n\nPreviously, in _validateStdio we were using stdio.fd || stdio. If\nstdio.fd was falsy (or 0 in the case of stdin), then the entire stdio\nobject would be passed which could cause a crash.\n\nFixes: https://github.com/nodejs/node/issues/2721\nPR-URL: https://github.com/nodejs/node/pull/2727\nReviewed-By: silverwind - Roman Reiss <me@silverwind.io>\nReviewed-By: cjihrig - Colin Ihrig <cjihrig@gmail.com>\nReviewed-By: indutny - Fedor Indutny <fedor.indutny@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nodejs/node/commits/c17ed0679ed1842c12a7a2f5df82fb300308f742"}]}