mirror of https://github.com/OISF/suricata
profiling: fix profiling with sample rate
Rules profiling was returning invalid results when used with sample rate. The problem was that the sample condition was run twice in the packet flow. As a result, the second pass was not initializing the variable storing the initial CPU ticks and the resulting performance counters were reporting invalid values. Bug: #4836.pull/6629/head
parent
16f4e5f31c
commit
6d5f59696d
Loading…
Reference in New Issue