From: Ofir Gal <ofir.gal@volumez.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: shinichiro.kawasaki@wdc.com, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org, dwagner@suse.de,
chaitanyak@nvidia.com, yukuai3@huawei.com,
linux-raid@vger.kernel.org
Subject: Re: [PATCH blktests v4 2/2] md: add regression test for "md/md-bitmap: fix writing non bitmap pages"
Date: Sun, 21 Jul 2024 17:40:47 +0300 [thread overview]
Message-ID: <eb9475e5-5a86-4331-8dfa-55e342e1cf37@volumez.com> (raw)
In-Reply-To: <8aac874e-f4f5-40a6-9e3c-1c88a8c49378@molgen.mpg.de>
On 7/21/24 13:23, Paul Menzel wrote:
> Dear Ofir,
>
>
> Thank you very much for submitting a test case.
>
> Am 21.07.24 um 09:11 schrieb Ofir Gal:
>> A bug in md-bitmap has been discovered by setting up a md raid on top of
>> nvme-tcp devices that has optimal io size larger than the allocated
>> bitmap.
>>
>> The following test reproduce the bug by setting up a md-raid on top of
>
> reproduce*s*
>
Thanks, will be applied in v5.
>> nvme-tcp device over ram device that sets the optimal io size by using
>> dm-stripe.
>
> For people ignorant of the test infrastructure, maybe add a line how to run this one test, and maybe even paste the output of the failed test.
>
blktests already documents pretty well how to run the tests, people
should read the docs of the infrastructure. The expected output exists
in a different file (md/001.out) as the infrastructure demands.
next prev parent reply other threads:[~2024-07-21 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 7:11 [PATCH blktests v4 0/2]md: add regression test for "md/md-bitmap: fix writing non bitmap pages" Ofir Gal
2024-07-21 7:11 ` [PATCH blktests v4 1/2] nvme: move helper functions to common/nvme Ofir Gal
2024-07-21 7:11 ` [PATCH blktests v4 2/2] md: add regression test for "md/md-bitmap: fix writing non bitmap pages" Ofir Gal
2024-07-21 10:23 ` Paul Menzel
2024-07-21 14:40 ` Ofir Gal [this message]
2024-07-29 12:19 ` [PATCH blktests v4 0/2]md: " Shinichiro Kawasaki
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=eb9475e5-5a86-4331-8dfa-55e342e1cf37@volumez.com \
--to=ofir.gal@volumez.com \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=shinichiro.kawasaki@wdc.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