Don't process detach and close as priority netmgr events

The detach (and possibly close) netmgr events can cause additional
callbacks to be called when under exclusive mode.  The detach can
trigger next queued TCP query to be processed and close will call
configured close callback.

Move the detach and close netmgr events from the priority queue to the
normal queue as the detaching and closing the sockets can wait for the
exclusive mode to be over.

(cherry picked from commit c2c2ec0c960941f34d3dbe0facacb04629406f8f)

diff --git a/lib/isc/netmgr/netmgr-int.h b/lib/isc/netmgr/netmgr-int.h
index 218da8810dbc25863a4fa3dac0f44ad542ac3ddb..05fde1a791b0a512c845f8a7de5a79204b1e3f44 100644 (file)
--- a/lib/isc/netmgr/netmgr-int.h
+++ b/lib/isc/netmgr/netmgr-int.h
@@ -286,6 +286,9 @@ typedef enum isc__netievent_type {
        netievent_readcb,
        netievent_sendcb,
 
+       netievent_detach,
+       netievent_close,
+
        netievent_task,
        netievent_privilegedtask,
 
@@ -304,8 +307,6 @@ typedef enum isc__netievent_type {
        netievent_tcpdnsstop,
 
        netievent_resume,
-       netievent_detach,
-       netievent_close,
 } isc__netievent_type;
 
 typedef union {