From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Xiao Ni <xni@redhat.com>
Cc: linux-raid@vger.kernel.org, ncroxon@redhat.com
Subject: Re: [PATCH V2 1/1] mdadm/Grow: Update new level when starting reshape
Date: Wed, 25 Sep 2024 09:51:39 +0200 [thread overview]
Message-ID: <20240925095139.0000066e@linux.intel.com> (raw)
In-Reply-To: <20240911085432.37828-2-xni@redhat.com>
On Wed, 11 Sep 2024 16:54:23 +0800
Xiao Ni <xni@redhat.com> wrote:
> +
> + /* new_level is introduced in kernel 6.12 */
> + if (!err && get_linux_version() >= 6012000 &&
> + sysfs_set_num(sra, NULL, "new_level",
> info->new_level) < 0)
> + err = errno;
Hi Xiao,
I realized that we would do this better by checking existence of new_level
sysfs file. This way, our solution is limited to kernel > 6.12 so, for example
redhat 9 with kernel 5.14 will never pass the condition. I know that you fixed
test issue but someone still may find this in real life.
I'm not going to rework it myself, I'm fine with current approach until
someone will report issue about that for older kernel.
If you are going to rework this, please left a comment about kernel version
that it was added, to let future maintainers know when the additional
verification can be removed.
Thanks,
Mariusz
next prev parent reply other threads:[~2024-09-25 7:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 8:54 [PATCH 00/10] mdadm tests fix Xiao Ni
2024-09-11 8:54 ` [PATCH V2 1/1] mdadm/Grow: Update new level when starting reshape Xiao Ni
2024-09-25 7:51 ` Mariusz Tkaczyk [this message]
2024-09-25 12:57 ` Xiao Ni
2024-09-11 8:54 ` [PATCH V2 2/2] mdadm/Grow: Update reshape_progress to need_back after reshape finishes Xiao Ni
2024-09-11 8:54 ` [PATCH 03/10] mdadm/Grow: Can't open raid when running --grow --continue Xiao Ni
2024-09-11 8:54 ` [PATCH v2 4/4] mdadm/Grow: sleep a while after removing disk in impose_level Xiao Ni
2024-09-11 8:54 ` [PATCH 05/10] mdadm/tests: wait until level changes Xiao Ni
2024-09-11 8:54 ` [PATCH 06/10] mdadm/tests: 07changelevels fix Xiao Ni
2024-09-11 8:54 ` [PATCH 07/10] mdadm/tests: Remove 07reshape5intr.broken Xiao Ni
2024-09-11 8:54 ` [PATCH 08/10] mdadm/tests: 07testreshape5 fix Xiao Ni
2024-09-11 8:54 ` [PATCH 09/10] mdadm/tests: remove 09imsm-assemble.broken Xiao Ni
2024-09-23 9:08 ` Mariusz Tkaczyk
2024-09-11 8:54 ` [PATCH 10/10] mdadm/Manage: record errno Xiao Ni
2024-09-23 8:51 ` [PATCH 00/10] mdadm tests fix 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=20240925095139.0000066e@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=ncroxon@redhat.com \
--cc=xni@redhat.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).