Revert "vfs_glusterfs: explain that/why we use the raw tevent_context in init_gluster...

This reverts commit b0af5715b0a7592a9728e0b76f653b9ab6228708.

See the discussion in

https://lists.samba.org/archive/samba-technical/2018-December/131731.html

for the reasoning behind this revert.

Signed-off-by: Ralph Boehme <slow@samba.org>
Reviewed-by: Volker Lendecke <vl@samba.org>
Reviewed-by: Stefan Metzmacher <metze@samba.org>

diff --git a/source3/modules/vfs_glusterfs.c b/source3/modules/vfs_glusterfs.c
index 9b623a4658b7cc5d97d1a863f15cd166add95e3b..c9d57b4b64632260aa7f1bda9599a62b335c0450 100644 (file)
--- a/source3/modules/vfs_glusterfs.c
+++ b/source3/modules/vfs_glusterfs.c
@@ -766,16 +766,7 @@ static bool init_gluster_aio(struct vfs_handle_struct *handle)
        read_fd = fds[0];
        write_fd = fds[1];
 
-       /*
-        * We use the raw tevent context here,
-        * as this is a global event handler.
-        *
-        * The tevent_req_defer_callback()
-        * calls will make sure the results
-        * of async calls are propagated
-        * to the correct tevent_context.
-        */
-       aio_read_event = tevent_add_fd(handle->conn->sconn->raw_ev_ctx,
+       aio_read_event = tevent_add_fd(handle->conn->sconn->ev_ctx,
                                        NULL,
                                        read_fd,
                                        TEVENT_FD_READ,