Since 'ticks' is an int, it may wrap around and cr_ticks at a certain

counter_rate will be greater than ticks, resulting in counter_ratecheck()
failure. To fix this take an absolute value of the difference between
ticks and cr_ticks.

Reported by:	jtl
Sponsored by:	Netflix
This commit is contained in:
Gleb Smirnoff 2018-06-15 21:36:16 +00:00
parent 31f494cdf5
commit 61f63f47b3
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=335242

View File

@ -140,7 +140,7 @@ counter_ratecheck(struct counter_rate *cr, int64_t limit)
val = cr->cr_over;
now = ticks;
if (now - cr->cr_ticks >= hz) {
if (abs(now - cr->cr_ticks) >= hz) {
/*
* Time to clear the structure, we are in the next second.
* First try unlocked read, and then proceed with atomic.
@ -151,7 +151,7 @@ counter_ratecheck(struct counter_rate *cr, int64_t limit)
* Check if other thread has just went through the
* reset sequence before us.
*/
if (now - cr->cr_ticks >= hz) {
if (abs(now - cr->cr_ticks) >= hz) {
val = counter_u64_fetch(cr->cr_rate);
counter_u64_zero(cr->cr_rate);
cr->cr_over = 0;