From: Mariusz Tkaczyk <mtkaczyk@kernel.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: song@kernel.org, linux-raid@vger.kernel.org, yukuai3@huawei.com,
yangerkun@huawei.com
Subject: Re: [PATCH] mdadm: fix --grow with --add for linear
Date: Tue, 31 Dec 2024 09:49:52 +0100 [thread overview]
Message-ID: <20241231094952.1fad40bb@mtkaczyk-private-dev> (raw)
In-Reply-To: <20241227060702.730184-1-yukuai1@huaweicloud.com>
On Fri, 27 Dec 2024 14:07:02 +0800
Yu Kuai <yukuai1@huaweicloud.com> wrote:
> From: Yu Kuai <yukuai3@huawei.com>
>
> For the case mdadm --grow with --add, the s.btype should not be
> initialized yet, hence BitmapUnknown should be checked instead of
> BitmapNone.
Hi Kuai,
For commit extra clarity it would be nice to include command you are
executing.
What if someone will do (not tested):
#mdadm --grow /dev/md0 --add /dev/sdx --bitmap=none
I think that it is perfectly valid, now it may work but I expect your
change to broke it.
I would say we need:
bool is_bitmap_set(struct shape *s) {
if (s.layout)
return true;
if (s.btype == BitmapNone || s.btype != BitmapUnknown)
return false;
return true;
}
And respect both cases. Setting property to default should never be a
mistake.
Has it some sense? If no, I miss some explanation in commit message (or
better comment).
>
> Noted that this behaviour should only support by md-linear, which is
> removed from kernel, howerver, it turns out md-linear is used widely
> in home NAS and we're planning to reintroduce it soon.
Wow. We get a lesson.
For the code, LGTM.
Thanks,
Mariusz
next prev parent reply other threads:[~2024-12-31 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 6:07 [PATCH] mdadm: fix --grow with --add for linear Yu Kuai
2024-12-31 8:49 ` Mariusz Tkaczyk [this message]
2025-01-26 8:22 ` Yu Kuai
2025-01-27 9:35 ` Mariusz Tkaczyk
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=20241231094952.1fad40bb@mtkaczyk-private-dev \
--to=mtkaczyk@kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yukuai1@huaweicloud.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;
as well as URLs for NNTP newsgroup(s).