Bug ID 1388985: The daemon dwbld uses 100% CPU when max port value configured in TMC port list

Last Modified: Dec 05, 2024

Affected Product(s):
BIG-IP AFM(all modules)

Known Affected Versions:
16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4

Fixed In:
17.1.2, 16.1.5

Opened: Oct 26, 2023

Severity: 3-Major

Symptoms

When Traffic Matching Criteria (TMC) port list range is configured that includes maximum port value of 65535, counter is incremented till 65535 and wraps back to 0, as the variable used to store the counter is uint16_t.

Impact

The daemon dwbld consumes 100% CPU impacting system performance.

Conditions

- AFM license enabled. - Daemon dwbld enabled - Any TMC port list configured with maximum port value of 65535

Workaround

Avoid configuring maximum port value of 65535 in TMC port list range.

Fix Information

The counter is changed to uint32_t to avoid rollover when maximum port value is included in port list range.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips