initialize sockaddrdscp to prevent spurious output from 'named-checkconf -p'

(cherry picked from commit f8d753d452)
This commit is contained in:
Evan Hunt
2020-05-06 12:48:13 -07:00
parent 15367a148d
commit 1df4141279
3 changed files with 11 additions and 0 deletions
+4
View File
@@ -1,3 +1,7 @@
5405. [bug] 'named-checkconf -p' could include spurious text
in server-addresses statements due to an uninitialized
DSCP value. [GL #1812]
5404. [bug] 'named-checkconf -z' could incorrectly indicate
success if errors were found in one view but not in a
subsequent one. [GL #1807]
+6
View File
@@ -104,6 +104,12 @@ view "second" {
};
zone-statistics no;
};
zone "example3" {
type static-stub;
server-addresses {
1.2.3.4;
};
};
zone "clone" {
in-view "first";
};
+1
View File
@@ -2522,6 +2522,7 @@ parse_netaddr(cfg_parser_t *pctx, const cfg_type_t *type, cfg_obj_t **ret) {
CHECK(cfg_create_obj(pctx, type, &obj));
CHECK(cfg_parse_rawaddr(pctx, flags, &netaddr));
isc_sockaddr_fromnetaddr(&obj->value.sockaddr, &netaddr, 0);
obj->value.sockaddrdscp.dscp = -1;
*ret = obj;
return (ISC_R_SUCCESS);
cleanup: