Merge pull request #340 from u5surf/fix_use_ngx_shmtx_lock_in_dump

Fix use ngx_shmtx_lock in dump_execute

Author: u5surf

src/ngx_http_vhost_traffic_status_dump.c

@@ -187,6 +187,7 @@ ngx_http_vhost_traffic_status_dump_execute(ngx_event_t *ev)
     ssize_t                               n;
     ngx_fd_t                              fd;
     ngx_file_t                            file;
+    ngx_slab_pool_t                      *shpool;
     ngx_http_vhost_traffic_status_ctx_t  *ctx;
 
     ctx = ev->data;
@@ -218,8 +219,14 @@ ngx_http_vhost_traffic_status_dump_execute(ngx_event_t *ev)
         return NGX_ERROR;
     }
 
+    shpool = (ngx_slab_pool_t *) ctx->shm_zone->shm.addr;
+
+    ngx_shmtx_lock(&shpool->mutex);
+
     ngx_http_vhost_traffic_status_dump_node_write(ev, &file, ctx->rbtree->root);
 
+    ngx_shmtx_unlock(&shpool->mutex);
+
     ngx_http_vhost_traffic_status_file_unlock(&file);
     ngx_http_vhost_traffic_status_file_close(&file);