To keep its cache database efficient, named running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, named may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured max-cache-size limit to be significantly exceeded.
Created bind tracking bugs for this issue: Affects: fedora-all [bug 2264065]
Created dhcp tracking bugs for this issue: Affects: fedora-all [bug 2264362]
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2024:1647 https://access.redhat.com/errata/RHSA-2024:1647
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Extended Update Support Via RHSA-2024:1648 https://access.redhat.com/errata/RHSA-2024:1648
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:1781 https://access.redhat.com/errata/RHSA-2024:1781
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:1789 https://access.redhat.com/errata/RHSA-2024:1789
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Extended Update Support Via RHSA-2024:1800 https://access.redhat.com/errata/RHSA-2024:1800
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Extended Update Support Via RHSA-2024:1803 https://access.redhat.com/errata/RHSA-2024:1803
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:2551 https://access.redhat.com/errata/RHSA-2024:2551