From: Andrew Morton <akpm@linux-foundation.org>
To: Josh Law <objecting@objecting.org>
Cc: linux-kernel@vger.kernel.org, hlcj1234567@gmail.com
Subject: Re: [PATCH] lib/assoc_array: fix stale nr_leaves_on_tree after gc
Date: Wed, 18 Mar 2026 10:23:19 -0700 [thread overview]
Message-ID: <20260318102319.0db807e1dc3e29fd1cde68b1@linux-foundation.org> (raw)
In-Reply-To: <20260318164959.85841-1-objecting@objecting.org>
On Wed, 18 Mar 2026 16:49:59 +0000 Josh Law <objecting@objecting.org> wrote:
> In assoc_array_gc(), assoc_array_apply_edit() publishes the new tree
> root before nr_leaves_on_tree is updated, creating a window where the
> tree is visible with a stale leaf count. Move the nr_leaves_on_tree
> assignment before assoc_array_apply_edit() so the count is consistent
> when the new root becomes visible.
>
> ...
>
> --- a/lib/assoc_array.c
> +++ b/lib/assoc_array.c
> @@ -1711,8 +1711,8 @@ int assoc_array_gc(struct assoc_array *array,
>
> gc_complete:
> edit->set[0].to = new_root;
> - assoc_array_apply_edit(edit);
> array->nr_leaves_on_tree = nr_leaves_on_tree;
> + assoc_array_apply_edit(edit);
> return 0;
But assoc_array_apply_edit() alters array->nr_leaves_on_tree and now we
immediately overwrite that alteration?
next prev parent reply other threads:[~2026-03-18 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 16:49 Josh Law
2026-03-18 17:23 ` Andrew Morton [this message]
2026-03-18 17:29 ` Josh Law
2026-03-18 18:36 ` Andrew Morton
2026-03-18 18:42 ` Josh Law
2026-03-18 17:43 ` Josh Law
-- strict thread matches above, loose matches on Subject: below --
2026-03-18 16:48 Josh Law
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=20260318102319.0db807e1dc3e29fd1cde68b1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hlcj1234567@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
all inboxes | Powered by JetHome®