Willy Tarreau f5cab82025 MINOR: fd: make sure to mark the thread as not stuck in fd_update_events() ... When I/O events are being processed, we want to make sure to mark the thread as not stuck. The reason is that some pollers (like poll()) which do not limit the number of FDs they report could possibly report a huge amount of FD all having to perform moderately expensive operations in the I/O callback (e.g. via mux-pt which forwards to the upper layers), making the watchdog think the thread is stuck since it does not schedule. Of course this must never happen but if it ever does we must be liberal about it. This should be backported to 2.0, where the situation may happen more easily due to the FD cache which can start to collect a large amount of events. It may be related to the report in issue #201 though nothing is certain about it.		2019-08-16 16:06:14 +02:00
..
common	CLEANUP: buffer: replace b_drop() with b_free()	2019-08-08 08:07:45 +02:00
import
proto	MINOR: fd: make sure to mark the thread as not stuck in fd_update_events()	2019-08-16 16:06:14 +02:00
types	MINOR: cli: add two new states to print messages on the CLI	2019-08-09 10:11:38 +02:00