From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: linux-raid@vger.kernel.org, jes@trained-monkey.org,
pmenzel@molgen.mpg.de, logang@deltatee.com, song@kernel.org,
yukuai3@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH tests 2/5] tests: add a new test for rdev lifetime
Date: Wed, 24 May 2023 10:33:01 +0200 [thread overview]
Message-ID: <20230524103301.00007195@linux.intel.com> (raw)
In-Reply-To: <20230523133900.3149123-3-yukuai1@huaweicloud.com>
On Tue, 23 May 2023 21:38:57 +0800
Yu Kuai <yukuai1@huaweicloud.com> wrote:
> From: Yu Kuai <yukuai3@huawei.com>
>
> This test add and remove a underlying disk to raid concurretly, verify
> that the following problem is fixed:
As in previous patch, feel free to move it into separate directory.
This test is limited only to this particular problem you resolved because you
are verifying error message in dmesg. It has no additional value because
probability that this issue will ever more occur in the same shape is
minimal.
IMO you should check how "remove" and "add" are handled, if errors are
returned, if there is no trace in dmesg or if processes are not blocked in
kernel.
You can check for this error message as a additional step at the end of test
but not as a mandatory test pass criteria.
In current form it gives as a knowledge that particular kernel doesn't have your
fix, that is all. Because it is race, probably it is not impacting real life
scenarios, so that gives a weak motivation to backport the fix (only security
reasons matters).
I don't see that this particular scenario requires test. You need to make it
more valuable for the future.
Thanks,
Mariusz
next prev parent reply other threads:[~2023-05-24 8:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 13:38 [PATCH tests 0/5] tests: add some regression tests Yu Kuai
2023-05-23 13:38 ` [PATCH tests 1/5] tests: add a new test to check if pluged bio is unlimited for raid10 Yu Kuai
2023-05-24 7:53 ` Mariusz Tkaczyk
2023-05-24 8:26 ` Yu Kuai
2023-05-24 9:00 ` Mariusz Tkaczyk
2023-05-24 9:09 ` Yu Kuai
2023-05-23 13:38 ` [PATCH tests 2/5] tests: add a new test for rdev lifetime Yu Kuai
2023-05-24 8:33 ` Mariusz Tkaczyk [this message]
2023-05-24 9:05 ` Yu Kuai
2023-05-24 10:38 ` Mariusz Tkaczyk
2023-05-23 13:38 ` [PATCH tests 3/5] tests: support to skip checking dmesg Yu Kuai
2023-05-24 8:40 ` Mariusz Tkaczyk
2023-05-23 13:38 ` [PATCH tests 4/5] tests: add a regression test for raid10 deadlock Yu Kuai
2023-05-24 8:48 ` Mariusz Tkaczyk
2023-05-24 9:07 ` Yu Kuai
2023-05-23 13:39 ` [PATCH tests 5/5] tests: add a regression test for raid456 deadlock Yu Kuai
2023-05-24 9:09 ` Mariusz Tkaczyk
2023-05-24 7:56 ` [PATCH tests 0/5] tests: add some regression tests Paul Menzel
2023-05-24 9:11 ` 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=20230524103301.00007195@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=pmenzel@molgen.mpg.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.