{"push_id":1030709096,"size":1,"distinct_size":1,"ref":"refs/heads/slurm-15.08","head":"dcfa6ec034ad4ef96242c3cb3a6d25ae94851cff","before":"886df85b9a561cb7c3658f0e4aafdaaf1f5fbdd9","commits":[{"sha":"dcfa6ec034ad4ef96242c3cb3a6d25ae94851cff","author":{"email":"cdd4f874095045f4ae6670038cbbd05fac9d4802@schedmd.com","name":"Danny Auble"},"message":"Fix deadlock issue with burst_buffer/cray when a newly created burst\nbuffer is found.\n\nBug 2576\n\nWhat happened was a function was doing a double read lock which isn't\nawesome to begin with, but not really horrible (if all you are doing is\nread locks anyway).  The problem was after the first lock was locked a\ndifferent thread was going for a write lock and so when the second\nread lock came in it created deadlocked.","distinct":true,"url":"https://api.github.com/repos/SchedMD/slurm/commits/dcfa6ec034ad4ef96242c3cb3a6d25ae94851cff"}]}