{"push_id":1124904251,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"48eee55c085af819583dcd607efd7de07b943b5f","before":"6e7c849dcfddf3025927972401b78e196bbe95ea","commits":[{"sha":"aa351b8496fea80a2ae1f66992a43c81ca02c2dc","author":{"email":"bc4bbf83189bf2aa3b4ae434673d425054bbfadd@intel.com","name":"Marcin Ślusarz"},"message":"doc: document interaction with thread cancellation\n\nLibpmemobj is not cancellation-safe. The pool will never be corrupted\nbecause of canceled thread, but other threads may stall waiting on\nlocks taken by that thread. If application wants to use pthread_cancel(3),\nit must disable cancellation before calling libpmemobj APIs (see\npthread_setcancelstate(3) with PTHREAD_CANCEL_DISABLE) and re-enable\nit after. Deferring cancellation (pthread_setcanceltype(3) with\nPTHREAD_CANCEL_DEFERRED) is not safe enough, because libpmemobj\ninternally may call functions that are specified as cancellation points\nin POSIX API.","distinct":true,"url":"https://api.github.com/repos/ldorau/nvml/commits/aa351b8496fea80a2ae1f66992a43c81ca02c2dc"},{"sha":"48eee55c085af819583dcd607efd7de07b943b5f","author":{"email":"3bc9c5d00c378d71d680c6cb6f4878ed38d3c78a@intel.com","name":"Krzysztof Czurylo"},"message":"Merge pull request #841 from marcinslusarz/obj-cancel\n\ndoc: document interaction with thread cancellation","distinct":true,"url":"https://api.github.com/repos/ldorau/nvml/commits/48eee55c085af819583dcd607efd7de07b943b5f"}]}
{"actor":{"display_login":"ldorau"}}