From: Omar Sandoval <osandov@osandov.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, Omar Sandoval <osandov@fb.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH blktests 0/2] zbd: Support dm-crypt
Date: Mon, 26 Jul 2021 12:02:26 -0700 [thread overview]
Message-ID: <YP8GwrYGzv+Q/CQR@relinquished.localdomain> (raw)
In-Reply-To: <20210713101239.269789-1-shinichiro.kawasaki@wdc.com>
On Tue, Jul 13, 2021 at 07:12:37PM +0900, Shin'ichiro Kawasaki wrote:
> Linux kernel 5.9 added zoned block device support to dm-crypt. With this zoned
> dm-crypt device, zbd group test cases pass except zbd/007. This series makes
> required changes to allow the test case zbd/007 pass with zoned dm-cyrpt
> devices. The first patch adds dm-crypt support to the helper function
> _get_dev_container_and_sector(). The second patch wipes out broken data on the
> dm-crypt devices which was left after the test case run.
>
> Shin'ichiro Kawasaki (2):
> zbd/rc: Support dm-crypt
> zbd/007: Reset test target zones at test end
>
> tests/zbd/007 | 7 +++++++
> tests/zbd/rc | 20 ++++++++++++++------
> 2 files changed, 21 insertions(+), 6 deletions(-)
The patches look reasonable. Could you provide instructions on how to
run with zoned dm-crypt so I can run the tests?
next prev parent reply other threads:[~2021-07-26 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 10:12 [PATCH blktests 0/2] zbd: Support dm-crypt Shin'ichiro Kawasaki
2021-07-13 10:12 ` [PATCH blktests 1/2] zbd/rc: " Shin'ichiro Kawasaki
2021-07-13 13:59 ` Bart Van Assche
2021-07-14 11:13 ` Shinichiro Kawasaki
2021-07-13 10:12 ` [PATCH blktests 2/2] zbd/007: Reset test target zones at test end Shin'ichiro Kawasaki
2021-07-26 19:02 ` Omar Sandoval [this message]
2021-07-27 2:17 ` [PATCH blktests 0/2] zbd: Support dm-crypt 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=YP8GwrYGzv+Q/CQR@relinquished.localdomain \
--to=osandov@osandov.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=shinichiro.kawasaki@wdc.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).