From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Yu Kuai <yukuai1@huaweicloud.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.13 1/5] md/md-bitmap: factor behind write counters out from bitmap_{start/end}write()
Date: Mon, 27 Jan 2025 06:25:19 -0500 [thread overview]
Message-ID: <20250127041636-cfdee9945400d753@stable.kernel.org> (raw)
In-Reply-To: <20250127084928.3197157-2-yukuai1@huaweicloud.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 08c50142a128dcb2d7060aa3b4c5db8837f7a46a
WARNING: Author mismatch between patch and upstream commit:
Backport author: Yu Kuai<yukuai1@huaweicloud.com>
Commit author: Yu Kuai<yukuai3@huawei.com>
Status in newer kernel trees:
6.12.y | Not found
Note: The patch differs from the upstream commit:
---
1: 08c50142a128d ! 1: c5f3371866713 md/md-bitmap: factor behind write counters out from bitmap_{start/end}write()
@@ Metadata
## Commit message ##
md/md-bitmap: factor behind write counters out from bitmap_{start/end}write()
+ commit 08c50142a128dcb2d7060aa3b4c5db8837f7a46a upstream.
+
behind_write is only used in raid1, prepare to refactor
bitmap_{start/end}write(), there are no functional changes.
@@ Commit message
Reviewed-by: Xiao Ni <xni@redhat.com>
Link: https://lore.kernel.org/r/20250109015145.158868-2-yukuai1@huaweicloud.com
Signed-off-by: Song Liu <song@kernel.org>
+ Signed-off-by: Yu Kuai <yukuai1@huaweicloud.com>
## drivers/md/md-bitmap.c ##
@@ drivers/md/md-bitmap.c: __acquires(bitmap->lock)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
| stable/linux-6.6.y | Failed | N/A |
| stable/linux-6.1.y | Failed | N/A |
| stable/linux-5.15.y | Failed | N/A |
| stable/linux-5.10.y | Failed | N/A |
| stable/linux-5.4.y | Failed | N/A |
next prev parent reply other threads:[~2025-01-27 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 8:49 [PATCH 6.13 0/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-01-27 8:49 ` [PATCH 6.13 1/5] md/md-bitmap: factor behind write counters out from bitmap_{start/end}write() Yu Kuai
2025-01-27 11:25 ` Sasha Levin [this message]
2025-01-27 8:49 ` [PATCH 6.13 2/5] md/md-bitmap: remove the last parameter for bimtap_ops->endwrite() Yu Kuai
2025-01-27 8:49 ` [PATCH 6.13 3/5] md: add a new callback pers->bitmap_sector() Yu Kuai
2025-01-27 8:49 ` [PATCH 6.13 4/5] md/raid5: implement pers->bitmap_sector() Yu Kuai
2025-01-27 8:49 ` [PATCH 6.13 5/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-01-27 9:11 ` [PATCH 6.13 0/5] " Greg KH
2025-01-27 12:45 ` Greg KH
2025-02-06 1:46 ` Yu Kuai
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=20250127041636-cfdee9945400d753@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yukuai1@huaweicloud.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