Re: [PATCH 1/2] RPING: Make sure CQ event thread exits before destroying the CQ.

[Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>]

On 10/20/2010 03:35 PM, Jason Gunthorpe wrote:
> On Wed, Oct 20, 2010 at 10:23:25PM +0200, Bart Van Assche wrote:
>
>    
>> Please keep in mind that glibc uses locking internally for many file
>> I/O functions, e.g. printf() and fprintf().
>>      
> POSIX strictly defines what functions are, aren't and could be
> cancellation points, yes it is a surprising list. But, glibc won't
> break internally if you cancel any of its function calls. It has
> cleanup handlers and what not to protect itself.
>
> rping doesn't hold locks, or allocate memory in the cq_thread, so it
> seems OK to me. My main question would be what happens internally to
> ibverbs, and does it call any possible cancellation point while holding
> locks - is it missing cleanup handlers? Etc.
>
> Jason
>    

Hey Jason, do you have a pointer to the list of pthread cancellation 
points for Linux?

Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html