From 2bbc9d6f8d5f2c1b07fd6968314b7f530b7f3a4d Mon Sep 17 00:00:00 2001
From: Michal Židek <mzidek@redhat.com>
Date: Oct 23 2015 08:33:04 +0000
Subject: sysdb: Use get_next_domain instead of dom->next


Recent get_next_domain refactoring enabled
us to use it also for disabled domains.

Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>

---

diff --git a/src/db/sysdb_subdomains.c b/src/db/sysdb_subdomains.c
index 4b4bb0d..b2bf1a0 100644
--- a/src/db/sysdb_subdomains.c
+++ b/src/db/sysdb_subdomains.c
@@ -312,8 +312,8 @@ errno_t sysdb_update_subdomains(struct sss_domain_info *domain)
                                              SYSDB_SUBDOMAIN_TRUST_DIRECTION,
                                              0);
 
-        /* explicitly use dom->next as we need to check 'disabled' domains */
-        for (dom = domain->subdomains; dom; dom = dom->next) {
+        for (dom = domain->subdomains; dom;
+                dom = get_next_domain(dom, SSS_GND_INCLUDE_DISABLED)) {
             if (strcasecmp(dom->name, name) == 0) {
                 sss_domain_set_state(dom, DOM_ACTIVE);