From: osandov@osandov.com (Omar Sandoval)
Subject: [PATCH 1/2 blktests] nvme: add udevadm settle before disconnecting
Date: Mon, 11 Mar 2019 13:36:43 -0700 [thread overview]
Message-ID: <20190311203643.GB1315@vader> (raw)
In-Reply-To: <20190306094643.10262-1-sagi@grimberg.me>
On Wed, Mar 06, 2019@01:46:42AM -0800, Sagi Grimberg wrote:
> otherwise we can see some I/O failures as udev didn't get enough time
> to do its thing.
Thanks, applied this one. I'll wait for your response on patch 2.
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> ---
> tests/nvme/008 | 2 ++
> tests/nvme/009 | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/tests/nvme/008 b/tests/nvme/008
> index d73ec7d6d97a..04ff0bda42e3 100755
> --- a/tests/nvme/008
> +++ b/tests/nvme/008
> @@ -41,6 +41,8 @@ test() {
> cat "/sys/block/${nvmedev}n1/uuid"
> cat "/sys/block/${nvmedev}n1/wwid"
>
> + udevadm settle
> +
> nvme disconnect -n "${subsys_name}"
>
> _remove_nvmet_subsystem_from_port "${port}" "${subsys_name}"
> diff --git a/tests/nvme/009 b/tests/nvme/009
> index a46168123c56..81e61f99aba5 100755
> --- a/tests/nvme/009
> +++ b/tests/nvme/009
> @@ -37,6 +37,8 @@ test() {
> cat "/sys/block/${nvmedev}n1/uuid"
> cat "/sys/block/${nvmedev}n1/wwid"
>
> + udevadm settle
> +
> nvme disconnect -n "${subsys_name}"
>
> _remove_nvmet_subsystem_from_port "${port}" "${subsys_name}"
> --
> 2.17.1
>
prev parent reply other threads:[~2019-03-11 20:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 9:46 [PATCH 1/2 blktests] nvme: add udevadm settle before disconnecting Sagi Grimberg
2019-03-06 9:46 ` [PATCH 2/2 blktests] nvme: test out-of-range I/O access Sagi Grimberg
2019-03-06 20:08 ` Chaitanya Kulkarni
2019-03-06 20:28 ` Sagi Grimberg
2019-03-06 20:31 ` Chaitanya Kulkarni
2019-03-07 7:45 ` Johannes Thumshirn
2019-03-11 20:35 ` Omar Sandoval
2019-03-11 22:14 ` Sagi Grimberg
2019-03-11 22:21 ` Omar Sandoval
2019-03-11 22:28 ` Sagi Grimberg
2019-03-06 19:53 ` [PATCH 1/2 blktests] nvme: add udevadm settle before disconnecting Chaitanya Kulkarni
2019-03-11 20:36 ` 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=20190311203643.GB1315@vader \
--to=osandov@osandov.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