[Bug nptl/12683] Race conditions in pthread cancellation

["dan at censornet dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=12683

--- Comment #27 from Dan Searle <dan at censornet dot com> ---
(In reply to Rich Felker from comment #26)
> I don't think this is the bug you're seeing. If it were, use of async
> cancellation would only make it worse. But the symptoms you'd see from this
> bug would be things like side effects of a function having happened despite
> it getting cancelled.
> 
> If you're seeing 100% cpu load from threads in recv, the most likely
> explanation is that the socket you're reading from is in EOF status (remote
> sending end closed), so that recv immediately returns zero. Repeatedly
> attempting to read in this situation would be an application bug, not
> anything related to glibc.

Thanks Rich, your suggestion made me think to look through the code paths again
and you are quite right, there was an infinite loop in there, not obvious but I
found it.

In light of the current problems with cancellable threads and syscalls, I'm
going to disable cancelation during the main job execution (where all the
recv() can poll()) call are, just in case this bug is causing problems I'm
unaware of.

Many thanks, you saved me a lot of hair pulling :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.