Max Kellermann 4d3adaa557
event/SocketEvent: erase IMPLICIT_FLAGS in Cancel{Read,Write}() ...
Without this, calling CancelRead() after ScheduleRead() would leave
the HANGUP scheduled, and the caller could receive HANGUP events over
and over which are never properly handled, leading to a busy loop.
The semantics of this API are hard to get right, because the
IMPLICIT_FLAGS (a property of epoll) are somewhat weird. But it seems
that this change repairs a side effect of the SocketEvent interface
that seemed counterintuitive.
2024-05-06 12:48:42 +02:00
2023-03-06 14:59:48 +01:00
2023-03-12 19:53:03 +01:00
2024-04-03 20:43:40 +02:00
2024-04-03 20:43:40 +02:00
2023-03-12 20:02:54 +01:00
2023-03-12 20:02:54 +01:00
2023-03-12 20:02:54 +01:00
2023-03-06 14:59:48 +01:00
2023-11-21 20:47:25 +01:00
2023-03-12 20:02:54 +01:00
2023-03-12 20:02:54 +01:00
2023-03-21 11:00:41 +01:00
2023-03-12 19:53:03 +01:00
2023-03-06 14:59:48 +01:00
2023-11-21 20:47:29 +01:00
2024-04-03 21:30:59 +02:00
2023-09-27 11:39:55 +02:00
2023-09-27 10:36:56 +02:00
2023-03-12 20:02:54 +01:00
2023-03-06 14:59:48 +01:00
2023-03-12 20:02:54 +01:00
2024-04-10 13:36:05 +02:00
2023-10-15 10:51:06 +02:00
2023-09-26 15:47:09 +02:00
2023-09-26 15:47:09 +02:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2024-04-03 21:30:59 +02:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2023-11-02 10:48:21 +01:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2023-03-12 19:53:03 +01:00
2023-03-06 14:59:48 +01:00
2023-09-19 11:22:39 +02:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2023-03-12 20:02:54 +01:00
2024-05-06 12:48:42 +02:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2024-04-03 21:30:59 +02:00
2024-04-03 21:30:59 +02:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2023-05-22 21:57:18 +02:00
2023-05-22 21:57:18 +02:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2023-03-06 14:59:48 +01:00
2023-03-12 19:53:03 +01:00
4d3adaa557