rt: Stop using atomic ops on rust_kernel::live_tasks

These ops are all done within spitting distance of a suitable lock,
so just protect it with the lock.

1 files changed, 4 insertions, 3 deletions

diff --git a/src/rt/rust_kernel.h b/src/rt/rust_kernel.h
index ff892aea303..917444b2bbd 100644
--- a/src/rt/rust_kernel.h
+++ b/src/rt/rust_kernel.h
@@ -22,12 +22,13 @@ public:
 private:
     rust_scheduler *sched;
 
+    // Protects live_tasks, max_task_id and task_table
+    lock_and_signal task_lock;
     // Tracks the number of tasks that are being managed by
     // schedulers. When this hits 0 we will tell all schedulers
     // to exit.
-    volatile int live_tasks;
-    // Protects max_task_id and task_table
-    lock_and_signal task_lock;
+    int live_tasks;
+    // The next task id
     rust_task_id max_task_id;
     hash_map<rust_task_id, rust_task *> task_table;