{"push_id":1897765486,"size":1,"distinct_size":1,"ref":"refs/heads/issue-6414","head":"14b3adddc27c8f12180f18314c5715e46709c97e","before":"63fa50c360cec978c4327d01879fca3dde4e33e5","commits":[{"sha":"14b3adddc27c8f12180f18314c5715e46709c97e","author":{"name":"Brian Behlendorf","email":"a858f2314cfaacf8f584edaf19860167d645669b@llnl.gov"},"message":"Fix allocation race\n\nWhen performing concurrent object allocations using the new\nmulti-threaded allocator and large dnodes it's possible to\nallocate overlapping large dnodes.\n\nThis case should have been handled by detecting an error\nreturned by dnode_hold_impl().  But that logic only checked\nthe returned dnp was not-NULL, and the dnp variable was not\nreset to NULL when retrying.\n\nResolve the issue by properly checking the return value of\ndnode_hold_impl().\n\nReviewed-by: Ned Bass <bass6@llnl.gov>\nSigned-off-by: Brian Behlendorf <behlendorf1@llnl.gov>","distinct":true,"url":"https://api.github.com/repos/behlendorf/zfs/commits/14b3adddc27c8f12180f18314c5715e46709c97e"}]}
{"actor":{"display_login":"behlendorf"}}