mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daehyeon Ko <4ncienth@gmail.com>
To: akpm@linux-foundation.org, dhowells@redhat.com
Cc: jarkko@kernel.org, keyrings@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] assoc_array: discard shortcut when collapsing a leaf-only node
Date: Tue, 17 Nov 2026 22:41:20 +0900	[thread overview]
Message-ID: <179492189322.898945.11218563093551350188.assoc-array-status@gmail.com> (raw)
In-Reply-To: <20260925080548.2505640-1-4ncienth@gmail.com>

Hi,

A status update for this thread:

This patch was posted on September 25, reviewed by Jarkko, and is now
commit 37ff457ec467 ("assoc_array: discard shortcut when collapsing a
leaf-only node") at the tip of mm-hotfixes-stable.  It has also been
carried in linux-next.

Mainline commit 48691075b0ad ("assoc_array: don't chain a new shortcut
onto an existing one") has since been merged through 666539eecdf4 and
backported to the stable kernels.  As I understand it, the two patches
address the same consecutive-shortcut topology at different points:
37ff457ec467 removes the preceding shortcut during deletion collapse,
while 48691075b0ad replaces that shortcut when insertion would otherwise
put a new shortcut behind it.

The recent linux-next conflict with 1dbbde3bc4b8 ("lib: Remove
assoc_array") prompted me to record the relationship here.  This message
is not requesting a code change; it is only intended to connect the
public histories.  Please let me know if I have misunderstood the
relationship between the fixes.

Regards,
Daehyeon

      parent reply	other threads:[~2026-11-17 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25  8:05 Daehyeon Ko
2026-09-25 22:58 ` Jarkko Sakkinen
2026-09-29 19:04 ` Jarkko Sakkinen
2026-11-17 13:41 ` Daehyeon Ko [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=179492189322.898945.11218563093551350188.assoc-array-status@gmail.com \
    --to=4ncienth@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=jarkko@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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®