Commit 72a1c3f1 authored by Mukund Sivaraman's avatar Mukund Sivaraman
Browse files

Update notes.xml and CHANGES for #39567

parent 705cea35
......@@ -3,10 +3,15 @@
unexpected action could be taken. This has been
corrected. [RT #39481]
4121. [bug] When updating a response-policy zone via AXFR,
summary data about other policy zones could fall
out of sync. Ultimately this could trigger an
assertion failure in rpz.c. [RT #39567]
4121. [bug] On servers with one or more policy zones
configured as slaves, if a policy zone updated
during regular operation (rather than at
startup) using a full zone reload, such as via
AXFR, a bug could allow the RPZ summary data to
fall out of sync, potentially leading to an
assertion failure in rpz.c when further
incremental updates were made to the zone, such
as via IXFR. [RT #39567]
4120. [bug] A bug in RPZ could cause the server to crash if
policy zones were updated while recursion was
......
......@@ -644,12 +644,13 @@
</listitem>
<listitem>
<para>
On servers with more than one policy zone configured,
if one policy zone was updated via AXFR (especially when
the zone was very large) a race condition could allow the
RPZ summary data to fall out of sync with the policy zones,
potentially leading to an assertion failure in rpz.c.
[RT #39567]
On servers with one or more policy zones configured as
slaves, if a policy zone updated during regular operation
(rather than at startup) using a full zone reload, such as
via AXFR, a bug could allow the RPZ summary data to fall out
of sync, potentially leading to an assertion failure in
rpz.c when further incremental updates were made to the
zone, such as via IXFR. [RT #39567]
</para>
</listitem>
<listitem>
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment