This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug nptl/12683] Race conditions in pthread cancellation


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

--- Comment #26 from Rich Felker <bugdal at aerifal dot cx> ---
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.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]