Blame SOURCES/bind-dyndb-ldap-pspacek-0432-2-Prevent-crash-while-reloading-previously-invalid-but.patch

f3daad
From 9ae1320d0c71d95e0f9785afa922c5b3240ea66d Mon Sep 17 00:00:00 2001
f3daad
From: Petr Spacek <pspacek@redhat.com>
f3daad
Date: Fri, 22 Jul 2016 16:44:17 +0200
f3daad
Subject: [PATCH] Prevent crash while reloading previously invalid but now
f3daad
 valid DNS zone.
f3daad
f3daad
The crash happened under these circumstances:
f3daad
- a DNS zone (test.) has NS record relative to this zone (ns.test.)
f3daad
- the name pointed to by NS record did not have any A/AAAA records
f3daad
- restart BIND to enforce zone load
f3daad
- zone loading failed because of invalid NS record
f3daad
- missing A/AAAA record for name ns.test. was added
f3daad
-> CRASH!
f3daad
f3daad
https://fedorahosted.org/bind-dyndb-ldap/ticket/166
f3daad
---
f3daad
 src/ldap_helper.c | 1 +
f3daad
 1 file changed, 1 insertion(+)
f3daad
f3daad
diff --git a/src/ldap_helper.c b/src/ldap_helper.c
f3daad
index 681661b8910c8213030f38aa9ba38eee748d3109..12a743b095ba400373cb87653d26af82cc95c2ea 100644
f3daad
--- a/src/ldap_helper.c
f3daad
+++ b/src/ldap_helper.c
f3daad
@@ -3824,6 +3824,7 @@ update_record(isc_task_t *task, isc_event_t *event)
f3daad
 update_restart:
f3daad
 	rbtdb = NULL;
f3daad
 	ldapdb = NULL;
f3daad
+	zone_settings = NULL;
f3daad
 	ldapdb_rdatalist_destroy(mctx, &rdatalist);
f3daad
 	CHECK(zr_get_zone_dbs(inst->zone_register, &entry->zone_name, &ldapdb, &rbtdb));
f3daad
 	CHECK(dns_db_newversion(ldapdb, &version));
f3daad
-- 
f3daad
2.7.4
f3daad