{"push_id":707246447,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"785b45420146da28f13cf6b5239ecb87dc12f9c5","before":"459c97bc2839bbbbca985a39724b24fdeb732e1c","commits":[{"sha":"785b45420146da28f13cf6b5239ecb87dc12f9c5","author":{"email":"05e8181be3150e47da8fe2e1f18d381c75496ff4@google.com","name":"Dmitry Vyukov"},"message":"tsan: fix handling of dup2\n\nPreviously tsan modelled dup2(oldfd, newfd) as write on newfd.\nWe hit several cases where the write lead to false positives:\n1. Some software dups a closed pipe in place of a socket before closing\n   the socket (to prevent races actually).\n2. Some daemons dup /dev/null in place of stdin/stdout.\nOn the other hand we have not seen cases when write here catches real bugs.\nSo model dup2 as read on newfd instead.","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-submodule/commits/785b45420146da28f13cf6b5239ecb87dc12f9c5"}]}