An exhaustive list, no. But every would-be race hunter needs to build a
list of known blocking operations, even if it blocks only under unusual
circumstances. Then when you're reviewing code and you see a potential
block, you can look to see what operations might be affected.
And when you discover a new blocking operation (or one that you hadn't
realized could block), you should go back and re-review all the code in
light of the new information.
Regards,
Bill