The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: David Carlier <devnexen@gmail.com>,
	Josh Law <objecting@objecting.org>,
	Dennis Zhou <dennis@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] lib: fix compare_delta parameter order in percpu_counter_tree
Date: Mon, 16 Mar 2026 10:39:12 -0400	[thread overview]
Message-ID: <56516363-e004-4d83-a231-5fa70b2f541d@efficios.com> (raw)
In-Reply-To: <20260316143805.36805-1-devnexen@gmail.com>

On 2026-03-16 10:38, David Carlier wrote:
> The compare_delta() helper takes (delta, accuracy_neg, accuracy_pos),
> but every call site passes (delta, accuracy_pos, accuracy_neg) — the
> last two arguments are consistently swapped.
> 
> The documented invariant (include/linux/percpu_counter_tree.h) is:
> 
>    (precise_sum - under) <= approx_sum <= (precise_sum + over)
> 
> Which means precise_sum is in [approx_sum - over, approx_sum + under].
> 
> For a positive delta (v - approx_sum >= 0), accuracy_pos must be
> "under" (the maximum amount precise_sum can exceed approx_sum).
> For a negative delta, accuracy_neg must be "over". Since under > over
> always (batch_size * M vs (batch_size - 1) * M), swapping them causes
> false definitive results: the functions return 1 ("v > counter") when
> the correct answer is 0 (indeterminate).
> 
> This affects all comparison functions:
> - percpu_counter_tree_approximate_compare_value()
> - percpu_counter_tree_approximate_compare()
> - percpu_counter_tree_precise_compare_value()
> - percpu_counter_tree_precise_compare()
> 
> The precise variants are also affected because their approximate
> fast-path can short-circuit with a wrong result, skipping the precise
> sum computation.
> 
> Fix by swapping the parameter order in compare_delta() itself, since
> all call sites are consistently swapped.
> 
> Signed-off-by: David Carlier <devnexen@gmail.com>

Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

> ---
>   lib/percpu_counter_tree.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/percpu_counter_tree.c b/lib/percpu_counter_tree.c
> index 5c8fc2dcdc16..beb1144e6450 100644
> --- a/lib/percpu_counter_tree.c
> +++ b/lib/percpu_counter_tree.c
> @@ -458,7 +458,7 @@ long percpu_counter_tree_precise_sum(struct percpu_counter_tree *counter)
>   EXPORT_SYMBOL_GPL(percpu_counter_tree_precise_sum);
>   
>   static
> -int compare_delta(long delta, unsigned long accuracy_neg, unsigned long accuracy_pos)
> +int compare_delta(long delta, unsigned long accuracy_pos, unsigned long accuracy_neg)
>   {
>   	if (delta >= 0) {
>   		if (delta <= accuracy_pos)


-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com

      parent reply	other threads:[~2026-03-16 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 14:38 [PATCH 1/2] lib: fix compare_delta parameter order in percpu_counter_tree David Carlier
2026-03-16 14:38 ` [PATCH 2/2] lib: add kunit boundary tests for percpu_counter_tree comparisons David Carlier
2026-03-16 14:40   ` Mathieu Desnoyers
2026-03-16 15:13   ` Josh Law
2026-03-16 14:39 ` Mathieu Desnoyers [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56516363-e004-4d83-a231-5fa70b2f541d@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=akpm@linux-foundation.org \
    --cc=dennis@kernel.org \
    --cc=devnexen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=objecting@objecting.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox