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.
(cherry picked from commit 6d5f59696dda77e1e7b2c45f51413b76690da4e9)

diff --git a/src/util-profiling.c b/src/util-profiling.c
index 3fbcd6b6a48c7353653faa1cb20a1a16356c1119..b0b7551d1e7f4e768bcbaeac4bd1eea7bb2e16a8 100644 (file)
--- a/src/util-profiling.c
+++ b/src/util-profiling.c
@@ -1246,6 +1246,8 @@ int SCProfileRuleStart(Packet *p)
         return 1;
     }
 #endif
+    if (p->flags & PKT_PROFILE)
+        return 1;
     return 0;
 }