From: Namhyung Kim <namhyung@kernel.org>
To: Suchit Karunakaran <suchitkarunakaran@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] perf/lock: Fix non-atomic max/time and min_time updates in contention_data
Date: Tue, 21 Apr 2026 19:40:57 -0700 [thread overview]
Message-ID: <aeg1ORW2I-YLvpFL@google.com> (raw)
In-Reply-To: <20260419182754.143225-1-suchitkarunakaran@gmail.com>
Hello,
On Sun, Apr 19, 2026 at 11:57:54PM +0530, Suchit Karunakaran wrote:
> The update_contention_data() had a FIXME noting that max_time and
> min_time updates lacked atomicity. Two CPUs could simultaneously
> read a stale value, pass the comparison check and race on the
> write-back, with the smaller value potentially overwriting the
> larger one and silently corrupting the statistics.
>
> Fix this by replacing the bare conditional assignments with a
> bpf_loop()-based CAS retry loop. Each field tracks its own
> convergence independently via max_done/min_done flags in cas_ctx,
> so a successful CAS on one field is never retried even if the
> other field needs more attempts.
Interesting!
It looks like bpf_loop() is added at v5.17 - more than 4 years ago.
Then I think it's ok to have it now.
>
> Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
> ---
> .../perf/util/bpf_skel/lock_contention.bpf.c | 50 +++++++++++++++++--
> 1 file changed, 45 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/util/bpf_skel/lock_contention.bpf.c b/tools/perf/util/bpf_skel/lock_contention.bpf.c
> index 96e7d853b9ed..5c8431be674a 100644
> --- a/tools/perf/util/bpf_skel/lock_contention.bpf.c
> +++ b/tools/perf/util/bpf_skel/lock_contention.bpf.c
> @@ -175,6 +175,13 @@ struct mm_struct___new {
> struct rw_semaphore mmap_lock;
> } __attribute__((preserve_access_index));
>
> +struct cas_ctx {
> + struct contention_data *data;
> + u64 duration;
> + int max_done;
> + int min_done;
> +};
> +
> extern struct kmem_cache *bpf_get_kmem_cache(u64 addr) __ksym __weak;
>
> /* control flags */
> @@ -486,16 +493,49 @@ static inline s32 get_owner_stack_id(u64 *stacktrace)
> return -1;
> }
>
> +static long cas_min_max_cb(u64 idx, void *arg)
> +{
> + struct cas_ctx *ctx = arg;
> +
> + if (!ctx->max_done) {
> + u64 old_max = ctx->data->max_time;
> +
> + if (old_max >= ctx->duration) {
> + ctx->max_done = 1;
> + } else {
> + u64 r = __sync_val_compare_and_swap(
> + &ctx->data->max_time, old_max, ctx->duration);
> + if (r == old_max)
> + ctx->max_done = 1;
> + }
> + }
> +
> + if (!ctx->min_done) {
> + u64 old_min = ctx->data->min_time;
> +
> + if (old_min <= ctx->duration) {
> + ctx->min_done = 1;
> + } else {
> + u64 r = __sync_val_compare_and_swap(
> + &ctx->data->min_time, old_min, ctx->duration);
> + if (r == old_min)
> + ctx->min_done = 1;
> + }
> + }
> +
> + return (ctx->max_done && ctx->min_done) ? 1 : 0;
> +}
> +
> static inline void update_contention_data(struct contention_data *data, u64 duration, u32 count)
> {
> __sync_fetch_and_add(&data->total_time, duration);
> __sync_fetch_and_add(&data->count, count);
>
> - /* FIXME: need atomic operations */
> - if (data->max_time < duration)
> - data->max_time = duration;
> - if (data->min_time > duration)
> - data->min_time = duration;
> + struct cas_ctx ctx = {
> + .data = data,
> + .duration = duration,
> + .max_done = 0,
> + .min_done = 0,
> + };
> + bpf_loop(64, cas_min_max_cb, &ctx, 0);
> }
>
> static inline void update_owner_stat(u32 id, u64 duration, u32 flags)
> --
> 2.53.0
>
prev parent reply other threads:[~2026-04-22 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 18:27 [PATCH] perf/lock: Fix non-atomic max/time and min_time updates in contention_data Suchit Karunakaran
2026-04-22 2:40 ` Namhyung Kim [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=aeg1ORW2I-YLvpFL@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=suchitkarunakaran@gmail.com \
/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