Fixed conflicts between ext_res and litmus budget tracking

Problem:
When using litmus's budget enforcement, due various overheads, the
task's budget and the gedf_res's budget may differ a bit. When the task
overruns its budget but due to this difference still has budget
according to gedf_res, this can cause litmus to bug out due to error
checking in litmus's budget enforcement code.

Solution:
Made sure not to dispatch the task if it's out of budget in
gedf_task_dispatch_client

1 files changed, 6 insertions, 1 deletions

diff --git a/litmus/reservations/gedf_reservation.c b/litmus/reservations/gedf_reservation.c
index e5a19e6de663..e08d3f9799e8 100644
--- a/litmus/reservations/gedf_reservation.c
+++ b/litmus/reservations/gedf_reservation.c
@@ -8,6 +8,7 @@
 #include <litmus/bheap.h>
 #include <litmus/rt_domain.h>
 #include <litmus/jobs.h>
+#include <litmus/budget.h>
 #include <litmus/np.h>
 #include <litmus/sched_trace.h>
 #include <litmus/debug_trace.h>
@@ -208,7 +209,11 @@ static struct task_struct* gedf_task_dispatch_client(
         lt_t* time_slice,
         int cpu)
 {
-        return ((struct gedf_task_reservation*)res)->task;
+        struct gedf_task_reservation* tmp = (struct gedf_task_reservation*)res;
+        if (budget_exhausted(tmp->task))
+                return NULL;
+        else
+                return tmp->task;
 }
 
 static void gedf_replenish_budget(