Really fix flushing of data in client_close().
Now that we call fmt_exit_message() from client_close() we do not need to try to determine whether the read or write events were pending in the old base. We can't tell anyway because the active flag in the event was cleared when the old sudo event base was destroyed. It is correct to enable both the read and write events after formatting the ExitMessage.
This commit is contained in:
@@ -845,6 +845,9 @@ sudo_ev_pending_v1(struct sudo_event *ev, short events, struct timespec *ts)
|
||||
int ret = 0;
|
||||
debug_decl(sudo_ev_pending, SUDO_DEBUG_EVENT);
|
||||
|
||||
sudo_debug_printf(SUDO_DEBUG_INFO, "%s: event %p, flags 0x%x, events 0x%x",
|
||||
__func__, ev, ev->flags, ev->events);
|
||||
|
||||
if (!ISSET(ev->flags, SUDO_EVQ_INSERTED))
|
||||
debug_return_int(0);
|
||||
|
||||
|
Reference in New Issue
Block a user