Stop holding the write lock when the SLURM is loaded

There's no need to hold the lock, the SLURM loading action doesn't modify the current DB state; it's altering the new DB state, which will be utilized later to replace the current DB state (and that's where the lock is needed).

diff --git a/src/rtr/db/vrps.c b/src/rtr/db/vrps.c
index be7f3bddc76a0bb631cb992b7c5df6c28a14effe..03ed98eeff2fd3af1c6d93153b03156a79555f62 100644 (file)
--- a/src/rtr/db/vrps.c
+++ b/src/rtr/db/vrps.c
@@ -289,14 +289,14 @@ __vrps_update(bool *changed)
        if (error)
                return error;
 
-       rwlock_write_lock(&state_lock);
-
        error = slurm_apply(&new_base, &state.slurm);
        if (error) {
                rwlock_unlock(&state_lock);
                goto revert_base;
        }
 
+       rwlock_write_lock(&state_lock);
+
        if (state.base != NULL) {
                error = compute_deltas(state.base, new_base, &deltas);
                if (error) {