Linux block layer
 help / color / mirror / Atom feed
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>,
	Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH blktests] zbd/007: Add --force option to blkzone reset
Date: Mon, 15 Jun 2020 16:17:04 -0700	[thread overview]
Message-ID: <20200615231704.GB2642892@vader> (raw)
In-Reply-To: <20200608024458.881519-1-shinichiro.kawasaki@wdc.com>

On Mon, Jun 08, 2020 at 11:44:58AM +0900, Shin'ichiro Kawasaki wrote:
> The test case zbd/007 utilizes blkzone command from util-linux project
> to reset zones of test target devices. Recently, blkzone was modified to
> report EBUSY error when it was called to change zone status of devices
> used by the system. This avoids unintended zone status change by mistake
> and good for most of use cases.
> 
> However this change triggered failure of the test case zbd/007 with the
> EBUSY error. The test case executes blkzone to reset zones of block devices
> which the system maps to container devices such as dm-linear.
> 
> To avoid this failure, modify zbd/007 to check if blkzone supports --force
> option. And if it is supported, add it to blkzone command line. This option
> was introduced to blkzone to allow zone status change of devices even when
> the system use them.
> 
> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> ---
>  tests/zbd/007 | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)

Thanks, applied.

      reply	other threads:[~2020-06-15 23:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08  2:44 [PATCH blktests] zbd/007: Add --force option to blkzone reset Shin'ichiro Kawasaki
2020-06-15 23:17 ` Omar Sandoval [this message]

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=20200615231704.GB2642892@vader \
    --to=osandov@osandov.com \
    --cc=Chaitanya.Kulkarni@wdc.com \
    --cc=Damien.LeMoal@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