From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y v2] Revert "bcache: remove heap-related macros and switch to generic min_heap"
Date: Thu, 31 Jul 2025 18:20:09 -0400 [thread overview]
Message-ID: <1753977078-7402f072@stable.kernel.org> (raw)
In-Reply-To: <20250731130315.33984-1-visitorckw@gmail.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 48fd7ebe00c1cdc782b42576548b25185902f64c
Status in newer kernel trees:
6.15.y | Present (different SHA1: 875dd4b6b0f3)
Note: The patch differs from the upstream commit:
---
1: 48fd7ebe00c1 ! 1: eda391cecfa0 Revert "bcache: remove heap-related macros and switch to generic min_heap"
@@ Metadata
## Commit message ##
Revert "bcache: remove heap-related macros and switch to generic min_heap"
+ [ Upstream commit 48fd7ebe00c1cdc782b42576548b25185902f64c ]
+
This reverts commit 866898efbb25bb44fd42848318e46db9e785973a.
The generic bottom-up min_heap implementation causes performance
@@ Commit message
Cc: Kent Overstreet <kent.overstreet@linux.dev>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
+ Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
## drivers/md/bcache/alloc.c ##
@@ drivers/md/bcache/alloc.c: static void bch_invalidate_one_bucket(struct cache *ca, struct bucket *b)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-6.12.y | Success | Success |
prev parent reply other threads:[~2025-07-31 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 13:03 [PATCH 6.12.y v2] Revert "bcache: remove heap-related macros and switch to generic min_heap" Kuan-Wei Chiu
2025-07-31 22:20 ` Sasha Levin [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=1753977078-7402f072@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@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