From bb1487fef5d19a7b1536fc42e25a08f7d4c43e1b Mon Sep 17 00:00:00 2001 From: Stephen Gallagher Date: Wed, 9 Jun 2010 10:04:44 -0400 Subject: Check the correct variable for NULL after creating timer In several places, we were creating a new timer and assigning it to the tev variable, but then we were checking for NULL from the te variable (which, incidentally, is guaranteed never to be NULL in this situation) https://fedorahosted.org/sssd/ticket/523 --- src/providers/data_provider_callbacks.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/providers/data_provider_callbacks.c') diff --git a/src/providers/data_provider_callbacks.c b/src/providers/data_provider_callbacks.c index 8ed2e5b60..9d8946a84 100644 --- a/src/providers/data_provider_callbacks.c +++ b/src/providers/data_provider_callbacks.c @@ -99,7 +99,7 @@ static void be_run_cb_step(struct tevent_context *ev, struct tevent_timer *te, tev = tevent_add_timer(cb_ctx->be->ev, cb_ctx, soon, be_run_cb_step, cb_ctx); - if (!te) { + if (!tev) { DEBUG(0, ("Out of memory. Could not invoke callbacks\n")); goto final; } -- cgit