From: Glass Su <glass.su@suse.com>
To: Heming Zhao <heming.zhao@suse.com>
Cc: linux-raid@vger.kernel.org, hch@lst.de, ofir.gal@volumez.com,
yukuai3@huawei.com, Su Yue <l@damenly.org>
Subject: Re: [PATCH v2] md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb
Date: Mon, 3 Mar 2025 11:39:50 +0800 [thread overview]
Message-ID: <C20AD799-0E78-435B-AAC0-EB01E4E2EC93@suse.com> (raw)
In-Reply-To: <5925f944-be6a-4f49-9946-a77ef4d3c2f3@suse.com>
> On Mar 3, 2025, at 11:08, Heming Zhao <heming.zhao@suse.com> wrote:
>
> Hi Glass,
>
> The code looks good to me.
> The commit log needs to be revised.
>
> On 3/2/25 12:39, Su Yue wrote:
>> In clustermd, Separate write-intent-bitmaps are used for each cluster
>> node:
>
> Change 'Separate' to lowercase 'separate'.
>> 0 4k 8k 12k
>> -------------------------------------------------------------------
>> | idle | md super | bm super [0] + bits |
>> | bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] |
>> | bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits |
>> | bm bits [3, contd] | | |
>> So in node 1, pg_index in __write_sb_page() could equal to
>> bitmap->storage.file_pages. Then bitmap_limit will be calculated to
>> 0. md_super_write() will be called with 0 size.
>> That means node the first 4k sb area of node 1 will never be updated
>> through filemap_write_page().
>
> "That means node the ...", should remove the word 'node'?
Thanks. Fixed in v3.
—
Su
>
> - Heming
>
>> This bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.
>> Here use (pg_index % bitmap->storage.file_pages) to calculation of
>> bitmap_limit correct.
>> Fixes: ab99a87542f1 ("md/md-bitmap: fix writing non bitmap pages")
>> Signed-off-by: Su Yue <glass.su@suse.com>
>> ---
>> drivers/md/md-bitmap.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>> diff --git a/drivers/md/md-bitmap.c b/drivers/md/md-bitmap.c
>> index 23c09d22fcdb..9ae6cc8e30cb 100644
>> --- a/drivers/md/md-bitmap.c
>> +++ b/drivers/md/md-bitmap.c
>> @@ -426,8 +426,8 @@ static int __write_sb_page(struct md_rdev *rdev, struct bitmap *bitmap,
>> struct block_device *bdev;
>> struct mddev *mddev = bitmap->mddev;
>> struct bitmap_storage *store = &bitmap->storage;
>> - unsigned int bitmap_limit = (bitmap->storage.file_pages - pg_index) <<
>> - PAGE_SHIFT;
>> + unsigned long num_pages = bitmap->storage.file_pages;
>> + unsigned int bitmap_limit = (num_pages - pg_index % num_pages) << PAGE_SHIFT;
>> loff_t sboff, offset = mddev->bitmap_info.offset;
>> sector_t ps = pg_index * PAGE_SIZE / SECTOR_SIZE;
>> unsigned int size = PAGE_SIZE;
>> @@ -436,7 +436,7 @@ static int __write_sb_page(struct md_rdev *rdev, struct bitmap *bitmap,
>> bdev = (rdev->meta_bdev) ? rdev->meta_bdev : rdev->bdev;
>> /* we compare length (page numbers), not page offset. */
>> - if ((pg_index - store->sb_index) == store->file_pages - 1) {
>> + if ((pg_index - store->sb_index) == num_pages - 1) {
>> unsigned int last_page_size = store->bytes & (PAGE_SIZE - 1);
>> if (last_page_size == 0)
>
prev parent reply other threads:[~2025-03-03 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 4:39 [PATCH v2] md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb Su Yue
2025-03-03 3:08 ` Heming Zhao
2025-03-03 3:39 ` Glass Su [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=C20AD799-0E78-435B-AAC0-EB01E4E2EC93@suse.com \
--to=glass.su@suse.com \
--cc=hch@lst.de \
--cc=heming.zhao@suse.com \
--cc=l@damenly.org \
--cc=linux-raid@vger.kernel.org \
--cc=ofir.gal@volumez.com \
--cc=yukuai3@huawei.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