From: Heming Zhao <heming.zhao@suse.com>
To: Su Yue <glass.su@suse.com>, linux-raid@vger.kernel.org
Cc: hch@lst.de, ofir.gal@volumez.com, yukuai3@huawei.com, l@damenly.org
Subject: Re: [PATCH v3] md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb
Date: Mon, 3 Mar 2025 11:43:36 +0800 [thread overview]
Message-ID: <2d8b5981-7648-4f7c-8157-5d6bb0822bda@suse.com> (raw)
In-Reply-To: <20250303033918.32136-1-glass.su@suse.com>
On 3/3/25 11:39, Su Yue wrote:
> In clustermd, separate write-intent-bitmaps are used for each cluster
> node:
>
> 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 the first 4k sb area of node 1 will never be updated
> through filemap_write_page().
> This bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.
>
> Here use (pg_index % bitmap->storage.file_pages) to make calculation
> of bitmap_limit correct.
>
> Fixes: ab99a87542f1 ("md/md-bitmap: fix writing non bitmap pages")
> Signed-off-by: Su Yue <glass.su@suse.com>
Looks good to me
Reviewed-by: Heming Zhao <heming.zhao@suse.com>
> ---
> Changelog:
> v3:
> Amend commit message suggested by Heming.
> v2:
> Remove unintended change calling md_super_write().
> ---
> 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)
next prev parent reply other threads:[~2025-03-03 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 3:39 [PATCH v3] md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb Su Yue
2025-03-03 3:43 ` Heming Zhao [this message]
2025-03-05 1:25 ` Yu Kuai
2025-03-05 10:47 ` Su Yue
2025-03-13 3:00 ` 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=2d8b5981-7648-4f7c-8157-5d6bb0822bda@suse.com \
--to=heming.zhao@suse.com \
--cc=glass.su@suse.com \
--cc=hch@lst.de \
--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