public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Su Yue <l@damenly.org>
To: Su Yue <glass.su@suse.com>
Cc: linux-raid@vger.kernel.org,  song@kernel.org,  xni@redhat.com,
	linan122@huawei.com,  yukuai@fnnas.com,  heming.zhao@suse.com
Subject: Re: [PATCH v2 0/5] md: bitmap grow fixes
Date: Thu, 16 Apr 2026 22:10:08 +0800	[thread overview]
Message-ID: <bjfj6lof.fsf@damenly.org> (raw)
In-Reply-To: <20260407102625.5686-1-glass.su@suse.com> (Su Yue's message of "Tue, 7 Apr 2026 18:26:20 +0800")

On Tue 07 Apr 2026 at 18:26, Su Yue <glass.su@suse.com> wrote:

> Hi, This v2 series is to fixes bugs exposed by 
> mdadm/clustermd-autotest.
> The bugs are not cluster md only but also bitmap related.
>
> The series based on v7.0-rc7 passes tests with mdadm v4.6 
> without regression.
>
> v2:
>     Add a dummy bitmap operations per Kuai's suggestion.
>
> To Yu Kuai:
> A NULL group can't used for internal_bitmap_group since
> the entries from internal_bitmap_attrs should be under bitmap.
> So instead of sysfs_create_groups(), sysfs_create_group() and 
> sysfs_merge_group()
> are still needed /sigh.
>
> Su Yue (5):
>   md/md-bitmap: call md_bitmap_create,destroy in location_store
>   md/md-bitmap: add an extra sysfs argument to md_bitmap_create 
>   and
>     destroy
>   md/md-bitmap: add dummy bitmap ops for none to fix wrong 
>   bitmap offset
>   md: skip ID_BITMAP_NONE when show available bitmap types
>   md/md-bitmap: remove member group from bitmap_operations
>
Missing part should be added in v3:

diff --git a/drivers/md/md.c b/drivers/md/md.c
index 20a953676319..453b89941db2 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -6450,9 +6450,6 @@ static int start_dirty_degraded;

 int md_bitmap_create(struct mddev *mddev, bool create_sysfs)
  {
  -       if (mddev->bitmap_id == ID_BITMAP_NONE)
  -               return -EINVAL;
  -
}
>  drivers/md/md-bitmap.c   | 121 
>  ++++++++++++++++++++++++++++++++++++---
>  drivers/md/md-bitmap.h   |   3 +-
>  drivers/md/md-llbitmap.c |  13 ++++-
>  drivers/md/md.c          |  55 +++++++++---------
>  drivers/md/md.h          |   2 +
>  5 files changed, 155 insertions(+), 39 deletions(-)

      parent reply	other threads:[~2026-04-16 14:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 10:26 [PATCH v2 0/5] md: bitmap grow fixes Su Yue
2026-04-07 10:26 ` [PATCH v2 1/5] md/md-bitmap: call md_bitmap_create,destroy in location_store Su Yue
2026-04-13  7:47   ` Li Nan
2026-04-13 10:18     ` Su Yue
2026-04-15 10:34   ` Xiao Ni
2026-04-16 14:08     ` Su Yue
2026-04-07 10:26 ` [PATCH v2 2/5] md/md-bitmap: add an extra sysfs argument to md_bitmap_create and destroy Su Yue
2026-04-07 10:26 ` [PATCH v2 3/5] md/md-bitmap: add dummy bitmap ops for none to fix wrong bitmap offset Su Yue
2026-04-07 10:26 ` [PATCH v2 4/5] md: skip ID_BITMAP_NONE when show available bitmap types Su Yue
2026-04-13  8:15   ` Li Nan
2026-04-13 10:23     ` Su Yue
2026-04-07 10:26 ` [PATCH v2 5/5] md/md-bitmap: remove member group from bitmap_operations Su Yue
2026-04-16 14:10 ` Su Yue [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=bjfj6lof.fsf@damenly.org \
    --to=l@damenly.org \
    --cc=glass.su@suse.com \
    --cc=heming.zhao@suse.com \
    --cc=linan122@huawei.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=xni@redhat.com \
    --cc=yukuai@fnnas.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